[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043384#comment-16043384
]
Ishan Chattopadhyaya commented on SOLR-10574:
---------------------------------------------
Seems like David and Shawn both want data driven nature to be off by default
(from the configset point of view).
I'd like to pitch in that we do otherwise (i.e. lets make data driven as
default), and here are my thoughts:
I agree that data driven nature, as it stands, has problems. However, for a new
user, who only knows how to create a collection and index documents, the data
driven nature gets him far more ahead today than when he has data driven
disabled. In the latter scenario, he needs to know how to create schema fields
or know how to use dynamic fields (or worse, how to work with hand-edited
configsets). So, as a default, a new user is better served with data driven
nature being available without any extra steps. However, for a user who is
willing to add schema fields anyway (e.g. using schema API), this extra step to
disable data-driven doesn't seem very out of the place. Now, in 7x, IMO we
should try to improve the data driven nature in terms of handling all the
scenarios it currently struggles with, and try making it great again. Just my
723 satoshis (=$0.02).
Having said that, I am willing to go either way based on consensus here.
> 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: [email protected]
For additional commands, e-mail: [email protected]
