lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-10574) Choose a default configset for Solr 7
Date Fri, 09 Jun 2017 18:27:18 GMT

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

Yonik Seeley commented on SOLR-10574:
-------------------------------------

bq. If we have a _text_ field but don't copy anything to it, what good is it? 

It gives an easier starting point and a convention for when it is needed/desired.

bq. their first queries would all get zero hits since they'd inevitably just to a "q=some
terms"

How would they even know how to do that much?  What URL do they hit, and what parameters to
pass?  They must be following a tutorial or some documentation, no?

bq. Why not make everything multi-valued by default with data_driven?

I think it is... and if you've tried it, the experience is bad for anything but text fields.
 If you try to sort on one of those fields, or use one of them in a function query, you'll
get exceptions.  I *tried* writing a basic tutorial using schemaless in the past. I couldn't
do it and had to resort to dynamic fields.


> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message