[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987147#comment-15987147
]
Shawn Heisey commented on SOLR-10574:
-------------------------------------
I agree with [~dsmiley] regarding the default for schemaless mode. I think
it's a mistake that our default (basic_configs) configuration adds unknown
fields.
The idea of high level toggles for functionality is really cool, particularly
if they can be easily toggled within the admin UI.
I understand the appeal of schemaless mode, and I do not have any objection to
Solr having the capability, but I firmly believe that it should be disabled by
default. I have found that when the update processor guesses what type to use
for a field containing text, what it chooses is frequently incorrect for what a
user needs, which means that the user must re-index after they fix the
incorrect type. Older behavior (fail to index until unknown fields are added)
means there is less re-indexing.
> 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
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
