[
https://issues.apache.org/jira/browse/SOLR-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018678#comment-18018678
]
Christos Malliaridis commented on SOLR-17862:
---------------------------------------------
I can totally understand the painpoints and I believe that we can tackle this
in a way that will satisfy everyone. Maybe I am too fanatical about the new UI,
but I believe that it provides great opportunities to create a useful
abstraction layer for the user interacting with the Configsets, and encapsulate
legacy APIs that seem problematic so that we can later migrate them (in v2 API
I hope).
In the new UI the simplest form right now is to just provide a file editor and
features that allow the user to update configsets and be aware of the impact of
a change (changes affect X collections, a reload is required etc.). Later, I
believe that we can extend this capability and provide improved forms for
well-known files and syntaxes, like synonyms.txt for example, so that input
errors like typos can be avoided or identified early on.
I believe with new dedicated configset endpoints (see [new unfinished proposals
in the v2 API
spreadsheet|https://docs.google.com/spreadsheets/d/1HAoBBFPpSiT8mJmgNZKkZAPwfCfPvlc08m5jz3fQBpA/edit?gid=1878317994#gid=1878317994&range=35:39])
we can address security concerns (like privileges required to use these
endpoints) and start deprecating the old endpoints.
In the context of this bug, I believe updating the documentation and
deprecating the API endpoint by replacing it with a new v2 API endpoint like in
the proposal would be a great start.
> Config API is not per-collection; applies to all collections using the same
> configset
> -------------------------------------------------------------------------------------
>
> Key: SOLR-17862
> URL: https://issues.apache.org/jira/browse/SOLR-17862
> Project: Solr
> Issue Type: Bug
> Reporter: Chris M. Hostetter
> Priority: Major
>
> The "Config API" uses a URL path prefix of
> {{/api/collections/<<COLLECTION_NAME>>/config}} and [has documentation that
> says|https://solr.apache.org/guide/solr/latest/configuration-guide/config-api.html]...
> {quote}
> All Config API endpoints are collection-specific, meaning this API can
> inspect or modify the configuration for a single collection at a time.
> {quote}
> ...but this is a lie. Using the Config API to modify any aspect of a
> collection actually modifies the {{configoverlay.json}} in the configset, and
> impacts all collections using that configset.
> ----
> * The "Config API" should be changed to use some new a URL path prefix that
> is specific to the name of the configset (Example:
> {{/api/configset-props/<<CONFIGSET_NAME>>/}})
> * The Existing {{/api/collections/<<COLLECTION_NAME>>/config}} URL should be
> deprecated
> * Documentation should be updated accordingly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
