[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-10574:
----------------------------------------
Attachment: SOLR-10574.patch
bq. I looked at this patch and I see that update.autoCreateFields is set to
false in the config - i.e. data driven is disabled by default. I'm very pleased
with that default! But it's not consistent with what you said you did.
Yes, I wanted it to be true by default (to maintain previous behaviour). But I
don't have any strong opinion either way. What is the consensus here?
bq. Might the toggle mechanism be made easier somehow?
Couldn't find anything easier, that is also clean enough to not expose any
internal implementation specific details (e.g. concept like update chain, name
of the chain, etc.)
bq. I confess I remain a fan of "classic" (non-managed) configuration because I
can simply go in and edit a config file to what I want it to be (and I can read
the config) all without reading documentation. I can even search the config.
By hand, this line needs to be changed:
From:
{code}
<updateRequestProcessorChain name="add-unknown-fields-to-the-schema"
default="${update.autoCreateFields:true}"
processor="uuid,remove-blank,field-name-mutating,parse-boolean,parse-long,parse-double,parse-date,add-schema-fields">
{code}
To:
{code}
<updateRequestProcessorChain name="add-unknown-fields-to-the-schema"
default="false"
processor="uuid,remove-blank,field-name-mutating,parse-boolean,parse-long,parse-double,parse-date,add-schema-fields">
{code}
bq. The APIs require that I go lookup documentation somewhere and hope there's
a one-liner ready for me to paste in to curl. Even with the super cool v2 APIs,
it's not going to help me know that there's a special custom user property
"update.autoCreateFields" that can be toggled.
This is the one liner:
{code}
curl http://host:8983/solr/coll1/config -d '{"set-user-property":
{"update.autoCreateFields":"false"}}'
{code}
> Choose a default configset for Solr 7
> -------------------------------------
>
> Key: SOLR-10574
> URL: https://issues.apache.org/jira/browse/SOLR-10574
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: master (7.0)
>
> Attachments: SOLR-10574.patch, SOLR-10574.patch, SOLR-10574.patch
>
>
> Currently, the data_driven_schema_configs is the default configset when
> collections are created using the bin/solr script and no configset is
> specified.
> However, that may not be the best choice. We need to decide which is the best
> choice, out of the box, considering many users might create collections
> without knowing about the concept of a configset going forward.
> (See also SOLR-10272)
> Proposed changes:
> # Remove data_driven_schema_configs and basic_configs
> # Introduce a combined configset, {{_default}} based on the above two
> configsets.
> # Build a "toggleable" data driven functionality into {{_default}}
> Usage:
> # Create a collection (using _default configset)
> # Data driven / schemaless functionality is enabled by default; so just start
> indexing your documents.
> # If don't want data driven / schemaless, disable this behaviour: {code}
> curl http://host:8983/solr/coll1/config -d '{"set-user-property":
> {"update.autoCreateFields":"false"}}'
> {code}
> # Create schema fields using schema API, and index documents
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
