[
https://issues.apache.org/jira/browse/SOLR-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947230#comment-14947230
]
Erick Erickson commented on SOLR-8131:
--------------------------------------
Apologies in advance if I'm missing something here and don't get me wrong, I
love where this could go; "use solr/bin to set up your test cluster then go to
the admin UI to modify your configs" would simplify _greatly_ the new user
experience.
The current "use zkcli to update your config set after you make changes" is
_really_ clumsy and I've seen countless users confused by this, especially
misunderstanding of the bootstrapping options. Not to mention all the confusion
when a manual edit introduces a syntax error and we get "help me, all of the
sudden Solr doesn't start"....
However (you knew this was coming):
If this is the default, then the only way to modify the schema will be with the
Schema API, right? So rather than allow someone to get into the schema file and
do a bunch of manual edits we'll force them to issue some long command like
below. I'm _NOT_ knocking it as an API call, it's a perfectly fine API, but I'm
sure not going to be happy typing it out 100 times for adding 100 fields to my
schema. Or writing a script.....
curl -X POST -H 'Content-type:application/json' --data-binary '{
"add-field":{
"name":"sell-by",
"type":"tdate",
"stored":true }
}' http://localhost:8983/solr/gettingstarted/schema
Sure, I can do all the mods to schema.xml first then switch to managed, but
that's obscure and certainly not something that someone would even think about
when just starting out. Or we can tell a novice to ignore the message about
"generated by... do not modify".
So my proposal would be do one of two things:
1> provide a "schema builder" as part of the new Angular Admin. Wouldn't have
to be anything all that complex to start and could grow over time. I can
imagine several approaches that would be more or less work, discuss this in any
tickets that come up I suppose.
or
2> enhance the bin/solr script to add/delete/replace schema elements. I'd
really like this option to allow changing one and only one parameter as an
option (syntax TBD) to make it simple to, say, just change stored from "true"
to "false" for some field/fieldType.
3> ???
I prefer <1> by _far_, but "progress not perfection" is the goal here. And this
could be quite a simple UI, we'd of course have to be careful that it didn't
upload arbitrary XML, but that should be relatively simple.
I'd go so far as advocate that whatever we decide about <1> or <2> be put in a
JIRA that _blocks_ this one. I can be talked out of that, especially if making
a UI that used the managed schema stuff under the covers would take a long time.
> Make ManagedIndexSchemaFactory as the default in Solr
> -----------------------------------------------------
>
> Key: SOLR-8131
> URL: https://issues.apache.org/jira/browse/SOLR-8131
> Project: Solr
> Issue Type: Wish
> Components: Data-driven Schema, Schema and Analysis
> Reporter: Shalin Shekhar Mangar
> Labels: difficulty-easy, impact-high
> Fix For: 5.4, Trunk
>
>
> The techproducts and other examples shipped with Solr all use the
> ClassicIndexSchemaFactory which disables all Schema APIs which need to modify
> schema. It'd be nice to be able to support both read/write schema APIs
> without needing to enable data-driven or schema-less mode.
> I propose to change all 5.x examples to explicitly use
> ManagedIndexSchemaFactory and to enable ManagedIndexSchemaFactory by default
> in trunk (6.x).
--
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
