[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044055#comment-16044055
]
Jan Høydahl commented on SOLR-10574:
------------------------------------
bq. I'm all for having the field in the schema, but not auto-copying all other
fields to it
Agree. Also ES ended up with [disabling the {{_all}}
field|https://github.com/elastic/elasticsearch/issues/19784] and instead
introduce a new {{all}} query type that auto expands the query to all textual
fields, with a constant score. I like that approach.
bq. We auto-detect multi-valued so we don't break if we come across multiple
values later, but then there are numerous things that only work with
single-valued fields
Could data-driven create a new field as single-valued at first, and somehow tag
it in {{IndexSchema}} as auto-detected so that if it sees multiple values for
the same field later it can update the field to multi valued before passing on
the update request. That would give the least surprises for a novice user, at
the same time as it would work the same for manually created single-value
fields. If each field in {{IndexSchema}} had a boolean {{autoCreated}} then it
would also be easier to QA a {{managed-schema}} since we'd know if a field is
explicitly defined or just added by the update chain.
> 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]
