[
https://issues.apache.org/jira/browse/SOLR-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043876#comment-16043876
]
Yonik Seeley commented on SOLR-10574:
-------------------------------------
bq. I think we should have the catch-all field enabled all the time.
I'm all for *having* the field in the schema, but not auto-copying all other
fields to it, doubling the indexing workload.
If people want to search across all fields, I think the right way is something
like edismax and wildcard support in the "qf" (query fields) parameter.
As far as data-drive-by-default... I'd be more in favor if it worked better.
The biggest issue I hit in the past was single/multi-valued problem. 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. We need fields that can be multi-valued, but act as single-valued when
they aren't.
bq. managed-schema.xml
+0 for the .xml extension. I prefer it to no extension, but there is back
compat to consider. I'd also prefer that if it get changed, we first look for
"managed-schema.xml", then "managed-schema", and then "schema.xml" to preserve
back compat.
> 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]
