[
https://issues.apache.org/jira/browse/SOLR-9163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368611#comment-15368611
]
Yonik Seeley edited comment on SOLR-9163 at 7/8/16 10:38 PM:
-------------------------------------------------------------
bq. commented out example stuff, most of which refers to fields that don't even
exist in the basic_configs schema
The schemas should be exactly the same now (except for the copyField).
bq. FWIW i think making "basic_configs" bigger [...] is a bad idea.
I sort of had the same thought when syncing these up... but I modeled the basic
after the schemaless (instead of vice-versa) because schemaless is what you get
by default when you create a core, and I didn't want to go breaking examples in
documentation.
bq. The intent behind basic_configs was to be just that: a very basic set of
configs.
Shouldn't schemaless just be about enabling that one feature?
was (Author: [email protected]):
bq. commented out example stuff, most of which refers to fields that don't even
exist in the basic_configs schema
The schema's should be exactly the same now (except for the copyField).
bq. FWIW i think making "basic_configs" bigger [...] is a bad idea.
I sort of had the same thought when syncing these up... but I modeled the basic
after the schemaless (instead of vice-versa) because schemaless is what you get
by default when you create a core, and I didn't want to go breaking examples in
documentation.
bq. The intent behind basic_configs was to be just that: a very basic set of
configs.
Shouldn't schemaless just be about enabling that one feature?
> Confusing solrconfig.xml in the downloaded solr*.zip
> ----------------------------------------------------
>
> Key: SOLR-9163
> URL: https://issues.apache.org/jira/browse/SOLR-9163
> Project: Solr
> Issue Type: Bug
> Reporter: Sachin Goyal
> Fix For: 6.2
>
> Attachments: SOLR-9163.patch, SOLR-9163.patch
>
>
> Here are the solrconfig.xml when I download and unzip solr:
> {code}
> find . -name solrconfig.xml
> ./solr-5.5.1/example/example-DIH/solr/db/conf/solrconfig.xml
> ./solr-5.5.1/example/example-DIH/solr/mail/conf/solrconfig.xml
> ./solr-5.5.1/example/example-DIH/solr/rss/conf/solrconfig.xml
> ./solr-5.5.1/example/example-DIH/solr/solr/conf/solrconfig.xml
> ./solr-5.5.1/example/example-DIH/solr/tika/conf/solrconfig.xml
> ./solr-5.5.1/example/files/conf/solrconfig.xml
> ./solr-5.5.1/server/solr/configsets/basic_configs/conf/solrconfig.xml
> ./solr-5.5.1/server/solr/configsets/data_driven_schema_configs/conf/solrconfig.xml
> ./solr-5.5.1/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml
> {code}
> Most likely, the ones I want to use are in server/solr/configsets, I assume.
> But then which ones among those three?
> Searching online does not provide much detailed information.
> And diff-ing among them yields even more confusing results.
> Example: When I diff basic_configs/conf/solrconfig.xml with
> data_driven_schema_configs/conf/solrconfig.xml, I am not sure why the latter
> has these extra constrcuts?
> # solr.LimitTokenCountFilterFactory and all the comments around it.
> # deletionPolicy class="solr.SolrDeletionPolicy"
> # Commented out infoStream file="INFOSTREAM.txt"
> # Extra comments for "Update Related Event Listeners"
> # indexReaderFactory
> # And so for lots of other constructs and comments.
> The point is that it is difficult to find out exactly what extra features in
> the latter are making it data-driven. Hence it is difficult to know what
> features I am losing by not taking the data-driven-schema.
> It would be good to sync the above 3 files together (each file should have
> same comments and differ only in the configuration which makes them
> different). Also, some good documentation should be put online about them
> otherwise it is very confusing for non-committers and vanilla-users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
