[
https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947311#comment-14947311
]
Upayavira commented on SOLR-8139:
---------------------------------
Now that collections UI is done and committed (via SOLR-4388) I plan to add
core admin style buttons along the top of the schema browser page, and to
rename the schema browser page to just "schema".
Those buttons will support these actions:
* add field (probably with the option to replace one)
* delete field
* add dynamic field (with option to replace one)
* delete dynamic field
* add (or replace) a copyField definition
* delete copyField definition
I plan to work on this this week.
> 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]
