lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6913) audit & cleanup "schema" in data_driven_schema_configs
Date Fri, 09 Jan 2015 16:29:36 GMT

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

Grant Ingersoll commented on SOLR-6913:
---------------------------------------

bq. My thinking was that the schemaless example should be minimal. In particular, if we don't
have a way for field types to be used (via (dynamic)field definitions or field guessing),
why include them? If the user can add fields, they can add field types too.

The main issue is that OOTB, this is the default and it thus leaves us pretty underpowered
for an OOTB experience.  Those Field Types have been in Solr for a long time and I think they
hold up reasonably well, so I would vote for putting them back in.

I think the big difference is, Solr experts come at the situation from edit schema/config
first.  New users come at data stores as let me manipulate my data first and then harden it
later.

> audit & cleanup "schema" in data_driven_schema_configs
> ------------------------------------------------------
>
>                 Key: SOLR-6913
>                 URL: https://issues.apache.org/jira/browse/SOLR-6913
>             Project: Solr
>          Issue Type: Task
>            Reporter: Hoss Man
>            Assignee: Steve Rowe
>            Priority: Blocker
>             Fix For: 5.0, Trunk
>
>         Attachments: SOLR-6913-trim-schema.patch, SOLR-6913-trim-schema.patch, SOLR-6913.patch
>
>
> the data_driven_schema_configs configset has some issues that should be reviewed carefully
& cleaned up...
> * currentkly includes a schema.xml file:
> ** this was previously pat of the old example to show the automatic "bootstraping" of
schema.xml -> managed-schema, but at this point it's just kind of confusing
> ** we should just rename this to "managed-schema" in svn - the ref guide explains the
bootstraping
> * the effective schema as it currently stands includes a bunch of copyFields & dynamicFields
that are taken wholesale from the techproducts example
> ** some of these might make sense to keep in a general example (ie: "\*_txt") but in
general they should all be reviewed.
> ** a bunch of this cruft is actually commented out already, but anything we don't want
to keep should be removed to eliminate confusion
> * SOLR-6471 added an explicit "_text" field as the default and made it a copyField catchall
(ie: "\*")
> ** the ref guide schema API example responses need to reflect the existence of this field:
https://cwiki.apache.org/confluence/display/solr/Schemaless+Mode
> ** we should draw heavy attention to this field+copyField -- both with a "/!\ NOTE" in
the refguide and call it out in solrconfig.xml & "managed-schema" file comments since
people who start with these configs may be suprised and wind up with a very bloated index



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message