[ 
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043022#comment-16043022
 ] 

Shawn Heisey commented on SOLR-10574:
-------------------------------------

bq. 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?

Repeating what I said earlier: I think field guessing should be off by default 
in basic_configs (or whatever we end up calling it), because (IMHO) it has a 
tendency to cause more problems than it solves.  While I understand a desire to 
maintain default settings from version to version, I believe that strict 
adherence to this only applies to new minor releases.

With 7.0, we have an opportunity to review past decisions, decide whether they 
are still relevant.  I think that every assumption and every default should be 
subject to review on every new major version.  I expect almost all of them to 
be retained after such a review ... massive changes would be a sign that we 
were doing a terrible job.

Related tangents:  1) Should we have a classic schema configset, or do we want 
to eventually remove the classic factory? 2) Should the filename for the 
managed schema regain its .xml extension?


> 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]

Reply via email to