gerlowskija opened a new pull request, #1453: URL: https://github.com/apache/solr/pull/1453
https://issues.apache.org/jira/browse/SOLR-16391 # Description Solr is in the process of migrating its v2 APIs over to a JAX-RS framework. This gives us a more feature-rich framework for expressing APIs, makes it easier for the APIs themselves to be more REST-ful and standardized, and also makes it easier for Solr to integrate with tooling such as OpenAPI, which can be used to autogenerate client bindings for a variety of different languages. But many non-JAX-RS APIs remain. # Solution This commit migrates the collection-creation API to the JAX-RS framework. It also makes a few cosmetic changes to the v2 APIs, to bring them closer into line with the more REST-ful design we're targeting for v2. As of this commit, the v2 API is now: * POST /api/collections {...} (See CreateCollectionRequestBody for the specific parameters accepted by the request body.) In order to keep the v2 API in line with any potential v1 changes, this commit moves the actual API logic for collection-creation over to the v2 definition. # Tests Still needs unit tests and there are a number of existing tests failing. # Checklist Please review the following and check all that apply: - [x] I have reviewed the guidelines for [How to Contribute](https://wiki.apache.org/solr/HowToContribute) and my code conforms to the standards described there to the best of my ability. - [x] I have created a Jira issue and added the issue ID to my pull request title. - [x] I have given Solr maintainers [access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to contribute to my PR branch. (optional but recommended) - [x] I have developed this patch against the `main` branch. - [ ] I have run `./gradlew check`. - [ ] I have added tests for my changes. - [ ] I have added documentation for the [Reference Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
