lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexandre Rafalovitch <arafa...@gmail.com>
Subject Re: Managed schema vs schema.xml
Date Tue, 07 Mar 2017 23:01:26 GMT
Actually, the main cross-references are from the solrconfig.xml, and
primarily from the Update Request Handler chain that creates the
"schemaless" effect. Then, I think you also have highlighters, etc.

I did that full analysis as a presentation at the last Solr
Revolution: https://www.slideshare.net/arafalov/rebuilding-solr-6-examples-layer-by-layer-lucenesolrrevolution-2016

Regards,
   Alex.
----
http://www.solr-start.com/ - Resources for Solr users, new and experienced


On 7 March 2017 at 17:18, Shawn Heisey <apache@elyograg.org> wrote:
> On 3/7/2017 1:32 PM, Phil Scadden wrote:
>>
>> I would have to say the "basic-config" seems distinctly more than basic.
>> It is still a huge file. I thought perhaps I could delete every unused field
>> type, but worried there were some "system" dependencies.
>
>
> This is definitely true.  Solr example configs tend towards including
> "everything and the kitchen sink".  Although this is good at illustrating
> everything that Solr can do, it is also VERY overwhelming to new users.  I
> have found that in my production configs, I tend to strip almost everything
> out and make them very lean.  I have kept a number of the schema fieldType
> definitions from the example, particularly those for basic data types, such
> as numeric fields.
>
> Most of the dependencies in a schema will be contained within the schema
> itself -- fieldTypes that are referenced by field definitions, etc.  There
> are a few other possible dependencies, such as a default field parameter in
> a search handler definition that lives in solrconfig.xml.
>
> Thanks,
> Shawn
>

Mime
View raw message