[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Upayavira updated SOLR-8139: ---------------------------- Attachment: add-field-with-omit-open.png > 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 > Attachments: add-field-with-omit-open.png, add-field.png > > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org