[
https://issues.apache.org/jira/browse/SOLR-16391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699687#comment-17699687
]
Jason Gerlowski commented on SOLR-16391:
----------------------------------------
I took a crack at the "Create Collection" API over the weekend and got pretty
far before running into a blocker. The path {{POST /api/collections}}, which
is used for collection-creation, also hosts a number of other
(legacy-framework) command-based APIs (e.g. create alias, delete alias,
set-alias-property, backup). Since both API frameworks claim that path,
V2HttpCall (which dispatches v2 requests) has doesn't have a good way to
understand whether it should use the legacy or JAX-RS framework to serve the
request.
The solution ultimately, is to get the remaining command-based APIs at that
path over to JAX-RS. But until then create-collection will be difficult to
migrate. I've pushed up my code to the branch
[here|https://github.com/gerlowskija/solr/tree/SOLR-16391-create-collection-jaxrs].
We can resume work on that branch and create a PR once the other APIs have
been migrated.
> Cosmetic improvements and migration to JAX-RS (collection, collection prop,
> core CRUD APIs)
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-16391
> URL: https://issues.apache.org/jira/browse/SOLR-16391
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Affects Versions: main (10.0)
> Reporter: Jason Gerlowski
> Priority: Major
> Labels: newdev
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As mentioned on SOLR-15781, the v2 API currently has an experimental
> designation, and the community has expressed an interest in using this period
> to update our v2 endpoints to be more REST-ful and consistent. The current
> plan is to follow the specific changes laid out in [this
> spreadsheet|https://docs.google.com/spreadsheets/d/1HAoBBFPpSiT8mJmgNZKkZAPwfCfPvlc08m5jz3fQBpA/edit?usp=sharing],
> though of course nothing there is set in stone and there are still warts to
> be worked out.
> While we're touching the code for these endpoints, we should also convert
> them to JAX-RS framework definitions. (This was initially tracked as a
> separate effort - see SOLR-16370 - but the edit that were required ended up
> overlapping so significantly with the "cosmetic" improvements here that in
> practice it almost always makes sense to do the two together.)
> This ticket plans to tackle making the changes required for Solr's collection
> and collection-prop CRUD APIs, as well as its collection-status APIs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
