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

Alexandre Rafalovitch commented on SOLR-10574:
----------------------------------------------

For _text_, what if we switched to eDisMax and used either *qf multifield 
expansion* or variable substitution to generate a synthetic field reference. As 
in: https://home.apache.org/~hossman/rev2016/#/6 or 
https://home.apache.org/~hossman/rev2016/#/17

And the field adding code would append to alias or expansion variable 
definition.

So, it would be something like

{quote}
    defType=edismax
    qf = id price autofields
    f.autofields.qf = auto1 auto2  auto3
{quote}

or
{quote}
   defType=edismax
   qf = id price $\{autofields}
   autofields = auto1 auto2 auto3
{quote}

This could actually solve some of the problems with explaining why the original 
field types are ignored during the default search, allow people to edit the 
mapping to remove some particularly-large fields, etc.

And as to big warnings, remember that the scheme gets rewritten after the first 
non-manual modifications. So, all the warnings and explanations in data-driven 
schema disappear as soon as it is actually used. A bit of a catch-22 there.

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

Reply via email to