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

Ishan Chattopadhyaya commented on SOLR-10574:
---------------------------------------------

Initially, I was looking at the toggleable flag to be set as follows:
{code}
Start with basic_configs configset, create a collection "test3" with that 
configset.

Enable data driven nature:

curl http://localhost:8983/solr/test3/config -d '{"add-initparams": {"name": 
"data-driven-nature", "path": "/update/**", "defaults": {"update.chain": 
"add-unknown-fields-to-the-schema"}}}'

Disable data driven nature:

curl http://localhost:8983/solr/test3/config -d '{"delete-initparams" : 
"data-driven-nature" }'
{code}

This currently works as of 6.x and this would've required minimal changes to 
achieve what we wanted (maybe just wrap that lengthy command into a shorter 
wrapper).

However, Noble informed me that, going forward, editing initparams is not the 
best choice. Upon his suggestion, and also Alexandre's, I am now looking at 
using paramsets and trying to construct the update chain (which is currently 
called "add-unknown-fields-to-the-schema") programmatically, and used upon the 
passing in of the appropriate parameter(s) for enabling/disabling data-driven 
nature. I shall post a patch soon.

> 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: 7.0
>
>
> 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:
> # Lets deprecate what we know as data_driven_schema_configs
> # Build a "toggleable" data driven functionality into the basic_configs 
> configset (and make it the default)



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