Details
-
Task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
Description
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:
curl http://host:8983/solr/coll1/config -d '{"set-user-property": {"update.autoCreateFields":"false"}}'
- Create schema fields using schema API, and index documents
Attachments
Attachments
Issue Links
- blocks
-
SOLR-10272 Use a default configset and make the configName parameter optional.
-
- Resolved
-
- is related to
-
SOLR-11033 Move out multi language field and fieldType to a separate example
-
- Open
-
1.
|
CREATE collection command to have parameter for turning on/off data driven nature |
|
Resolved | Unassigned | ||||||||
2.
|
Default configuration should use edismax for searching on all fields |
|
Open | Unassigned | ||||||||
3.
|
Add .xml extension to managed-schema |
|
Closed | Eric Pugh |
|
|||||||
4.
|
Add warning for disabling data driven nature before production |
|
Closed | Ishan Chattopadhyaya |