[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026908#comment-15026908 ] Upayavira commented on SOLR-8139: - Just me being sloppy. Fixed. > 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 > Fix For: 5.4 > > Attachments: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026903#comment-15026903 ] Alexandre Rafalovitch commented on SOLR-8139: - Still shows "fix-version: none". Though perhaps you update that later when you are doing the final sweep. Sorry, not sure of exact sequence of events. > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026889#comment-15026889 ] Alexandre Rafalovitch commented on SOLR-8139: - Is this actually resolved for 5.4? > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992089#comment-14992089 ] ASF subversion and git services commented on SOLR-8139: --- Commit 1712833 from [~upayavira] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1712833 ] SOLR-8139 Add missing bracket > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14992088#comment-14992088 ] ASF subversion and git services commented on SOLR-8139: --- Commit 1712832 from [~upayavira] in branch 'dev/trunk' [ https://svn.apache.org/r1712832 ] SOLR-8139 Add missing bracket > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989396#comment-14989396 ] ASF subversion and git services commented on SOLR-8139: --- Commit 1712536 from [~upayavira] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1712536 ] SOLR-8139, SOLR-8199 update CHANGES.txt > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989394#comment-14989394 ] ASF subversion and git services commented on SOLR-8139: --- Commit 1712535 from [~upayavira] in branch 'dev/trunk' [ https://svn.apache.org/r1712535 ] SOLR-8139, SOLR-8199 update CHANGES.txt > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989366#comment-14989366 ] ASF subversion and git services commented on SOLR-8139: --- Commit 1712533 from [~upayavira] in branch 'dev/branches/branch_5x' [ https://svn.apache.org/r1712533 ] SOLR-8139 Rename schema-browser to schema and add managed schema support > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989363#comment-14989363 ] ASF subversion and git services commented on SOLR-8139: --- Commit 1712532 from [~upayavira] in branch 'dev/trunk' [ https://svn.apache.org/r1712532 ] SOLR-8139 Rename schema-browser to schema and add managed schema support > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987167#comment-14987167 ] Alexandre Rafalovitch commented on SOLR-8139: - Please note that we are hiding the managed-file schema in the file browser as per SOLR-6992. Which may cause some confusion to people looking at the directory structure via the browser. Unless the whole file tab UI is going away of course. > 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: SOLR-8139.patch, SOLR-8139.patch, > add-field-with-errors.png, 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953072#comment-14953072 ] Jan Høydahl commented on SOLR-8139: --- This is cool! And we get extra testing of the APIs as well! > 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: SOLR-8139.patch, add-field-with-errors.png, > 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
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949445#comment-14949445 ] Upayavira commented on SOLR-8139: - [~steve_rowe] Perfect! Thx! > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[
https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949443#comment-14949443
]
Steve Rowe commented on SOLR-8139:
--
I think the config API should work - not sure how to get individual stuff, but
when I get the entire output from {{solr/core/config?wt=json}}, I see the
following for schemaless:
{noformat}
"schemaFactory":{"class":"ManagedIndexSchemaFactory"},
{noformat}
and the following for non-managed schema:
{noformat}
"schemaFactory":{"class":"ClassicIndexSchemaFactory"},
{noformat}
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14949386#comment-14949386 ] Upayavira commented on SOLR-8139: - [~steve_rowe] Rebuilding Solr fixed the above exception, taking with it seemingly any easy way for me to detect whether or not the schema is managed, at least via the API. I'd much rather we did it via the API than me have to scout around the configs looking for a _managedschema_ file or such. Possible? > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[
https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948400#comment-14948400
]
Upayavira commented on SOLR-8139:
-
[~steve_rowe] The one thing that would be really handy is a simple API that
tells me whether the managed schema is enabled or not.
Currently, if I call /solr//schema on a non-managed index, I get a
500 error and this:
java.lang.NoClassDefFoundError:
org/apache/solr/rest/schema/FieldCollectionResource
I can use that to detect a non-managed schema, but would much prefer it if in
that case it just returned: {"status": "schema not managed"}
Is that possible?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947399#comment-14947399 ] Steve Rowe commented on SOLR-8139: -- Awesome! > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ https://issues.apache.org/jira/browse/SOLR-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947381#comment-14947381 ] Upayavira commented on SOLR-8139: - This will only use the managed schema API. It will need to identify whether the schema is enabled. If it isn't, the buttons won't appear. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8139) Provide a way for the admin UI to utilize managed schema functionality
[ 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
