[
https://issues.apache.org/jira/browse/SOLR-16392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17611213#comment-17611213
]
ASF subversion and git services commented on SOLR-16392:
--------------------------------------------------------
Commit 087fe79dd1fbd75944f6467827b01a5ab9a12956 in solr's branch
refs/heads/main from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=087fe79dd1f ]
SOLR-16392: Support REST-ful path lookup in V2HttpCall (#1035)
Prior to this commit, V2HttpCall uses a rather crude heuristic to
determine whether a given API is a "container-level" or "core-level"
API. Namely, any path that a core/collection name can be parsed out of
is a "core" API that should live in the core-level PluginBag.
Conversely, anything else is a container-level API that should live in
the container-level PluginBag.
This happened to work for V2 because we initially chose our API paths
with this heuristic in mind. But the result is an API that's neither intuitive
nor user-friendly.
This PR takes a sort of "guess and check" approach, where we try
serving ambiguous requests from multiple Jersey apps in series, stopping
at the first one that doesn't spit out a quick NotFoundException.
> Cosmetic, REST-fulness improvements to v2 shard, replica, and replicaprop
> CRUD APIs
> -----------------------------------------------------------------------------------
>
> Key: SOLR-16392
> URL: https://issues.apache.org/jira/browse/SOLR-16392
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Affects Versions: main (10.0)
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Major
> Time Spent: 50m
> 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.
>
> This ticket plans to tackle making the changes required for Solr's shard,
> replica and replica-prop CRUD APIs, as described in that spreadsheet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
