[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042130#comment-16042130
]
David Smiley commented on SOLR-10574:
-------------------------------------
I think a patch modifying basic_configs would be easier to interpret for
code-review purposes as it would be a diff against existing files instead of
adding whole new files; and of course I didn't truly check what the differences
were. It might even be good to commit this in stages so that git change
tracking can better recognize what is going on (our future selves will thank
us!). For example, commit changes to basic configs such that it is what we
want the default to be, and then in another commit, both rename basic configs,
and remove the data driven configs.
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.
Might the toggle mechanism be made easier somehow? 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. 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.
> 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
>
>
> 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
