[
https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947360#comment-14947360
]
Erick Erickson commented on SOLR-8139:
--------------------------------------
I think you've just short-circuited the entire discussion about whether this
should be a blocker to SOLR-8131 ;).
Just to make sure I understand, this will use the managed schema API, right?
I'm gun-shy of uploading arbitrary XML...
And is there any way this can be enabled only if the collection's schema is
managed? It might be easy to infer by the presence of the managed file in the
config.....
> Provide a way for the admin UI to utilize managed schema functionality
> ----------------------------------------------------------------------
>
> Key: SOLR-8139
> URL: https://issues.apache.org/jira/browse/SOLR-8139
> Project: Solr
> Issue Type: Improvement
> Components: UI
> Reporter: Erick Erickson
> Assignee: Upayavira
>
> See the discussion at the related SOLR-8131. The suggestion there is to make
> managed schema the default in 6.0. To make the new-user experience much
> smoother in that setup, it would be great if the admin UI had a simple
> wrapper around the managed schema API.
> It would be a fine thing to have a way of bypassing the whole "find the magic
> config set, edit it in your favorite editor, figure out how to upload it via
> zkcli then reload the collection" current paradigm and instead be able to
> update the schema via the admin UI.
> This should bypass the issues with uploading arbitrary XML to the server that
> shot down one of the other attempts to edit the schema from the admin UI.
> This is mostly a marker. This could be a significant differentiator between
> the old and new admin UIs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
