-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Board Review: Azure Cognitive Search SDK for Java - preview 2 #791
Comments
@JonathanGiles @brjohnstmsft we have now closed all the bugs that were captured as part of this review. The new revision of the API is available at https://apiview.azurewebsites.net/Assemblies/Revisions/2abf935de65e4187964bea5b817872d6. Here is the full list of related work items. Please let us know what else is needed to close the review.
|
Looks good to me, except for one item: Bug 1632 | Consider renaming IndexGetStatisticsResult + model classes I've made the Swagger change for that in this PR. Please review and re-generate the Java SDK code accordingly. |
Thanks @brjohnstmsft will do as soon as our repo is resurrected. |
@brjohnstmsft code has been regenerated following the swagger spec changes as per https://github.com/navalev/azure-sdk-for-java-pr/pull/349 |
@brjohnstmsft @JonathanGiles can we close this? |
I'm fine closing it if @JonathanGiles is. |
The Basics
About this client library
Artifacts required (per language)
API view link: https://apiview.azurewebsites.net/Assemblies/Review/2abf935de65e4187964bea5b817872d6
Link to samples for champion scenarios: TBD - under development in https://github.com/navalev/azure-sdk-for-java-pr/
Champion Scenarios
Scenario 1: Setting up a basic search solution
This scenario assumes an existing search service
Scenario 2: Running a search solution
This scenario assumes an existing search solution as set up in scenario 1
Scenario 3: Refining search capabilities
This scenario assumes an existing search solution as set up in scenario 1
Agenda for the review
A board review is generally split into two parts, with additional meetings as required
Part 1 - Introducing the board to the service:
After part 1, you may schedule additional meetings with architects to refine the API and work on implementation.
Part 2 - the "GA" meeting
Thank you for your submission
The text was updated successfully, but these errors were encountered: