You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Tom Devel <de...@gmail.com> on 2015/03/06 17:21:38 UTC

Order of defining fields and dynamic fields in schema.xml

Hi,

I am running solr 5 using basic_configs and have a questions about the
order of defining fields and dynamic fields in the schema.xml file?

For example, there is a field "hierarchy.of.fields.Project" I am capturing
as below as "text_en_splitting", but the rest of the fields in this
hierarchy, I would like as "text_en"

Since the dynamicField with * is technically spanning over the Project
field, should its definition go above, or below the Project field?

<field name="hierarchy.of.fields.Project" type="text_en_splitting"
indexed="true"  stored="true"  multiValued="true" required="false" />
<dynamicField name="hierarchy.of.fields.*" type="text_en"
indexed="true"  stored="true"  multiValued="true" required="false" />


Or this case, I have a hierarchy where currently only one field should be
captured "another.hierarchy.of.fields.Description", the rest for now should
be just ignored. Is here any significance of which definition comes first?

<dynamicField name="another.hierarchy.of.*" type="text_en"
indexed="false"  stored="false"  multiValued="true" required="false" />
<dynamicField name="another.hierarchy.of.fields.Description"
type="text_en"    indexed="true"  stored="true"  multiValued="true"
required="false" />

Thanks for any hints,
Tom

Re: Order of defining fields and dynamic fields in schema.xml

Posted by Tom Devel <de...@gmail.com>.
Thats good to know.

On http://wiki.apache.org/solr/SchemaXml it also states about dynamicFields
that "you can create field rules that Solr will use to understand what
datatype should be used whenever it is given a field name that is not
explicitly defined, but matches a prefix or suffix used in a dynamicField. "

Thanks

On Fri, Mar 6, 2015 at 10:43 AM, Alexandre Rafalovitch <ar...@gmail.com>
wrote:

> I don't believe the order in file matters for anything apart from
> initParams section. The longer - more specific one - matches first.
>
>
> Regards,
>    Alex.
> ----
> Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
> http://www.solr-start.com/
>
>
> On 6 March 2015 at 11:21, Tom Devel <de...@gmail.com> wrote:
> > Hi,
> >
> > I am running solr 5 using basic_configs and have a questions about the
> > order of defining fields and dynamic fields in the schema.xml file?
> >
> > For example, there is a field "hierarchy.of.fields.Project" I am
> capturing
> > as below as "text_en_splitting", but the rest of the fields in this
> > hierarchy, I would like as "text_en"
> >
> > Since the dynamicField with * is technically spanning over the Project
> > field, should its definition go above, or below the Project field?
> >
> > <field name="hierarchy.of.fields.Project" type="text_en_splitting"
> > indexed="true"  stored="true"  multiValued="true" required="false" />
> > <dynamicField name="hierarchy.of.fields.*" type="text_en"
> > indexed="true"  stored="true"  multiValued="true" required="false" />
> >
> >
> > Or this case, I have a hierarchy where currently only one field should be
> > captured "another.hierarchy.of.fields.Description", the rest for now
> should
> > be just ignored. Is here any significance of which definition comes
> first?
> >
> > <dynamicField name="another.hierarchy.of.*" type="text_en"
> > indexed="false"  stored="false"  multiValued="true" required="false" />
> > <dynamicField name="another.hierarchy.of.fields.Description"
> > type="text_en"    indexed="true"  stored="true"  multiValued="true"
> > required="false" />
> >
> > Thanks for any hints,
> > Tom
>

Re: Order of defining fields and dynamic fields in schema.xml

Posted by Alexandre Rafalovitch <ar...@gmail.com>.
I don't believe the order in file matters for anything apart from
initParams section. The longer - more specific one - matches first.


Regards,
   Alex.
----
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/


On 6 March 2015 at 11:21, Tom Devel <de...@gmail.com> wrote:
> Hi,
>
> I am running solr 5 using basic_configs and have a questions about the
> order of defining fields and dynamic fields in the schema.xml file?
>
> For example, there is a field "hierarchy.of.fields.Project" I am capturing
> as below as "text_en_splitting", but the rest of the fields in this
> hierarchy, I would like as "text_en"
>
> Since the dynamicField with * is technically spanning over the Project
> field, should its definition go above, or below the Project field?
>
> <field name="hierarchy.of.fields.Project" type="text_en_splitting"
> indexed="true"  stored="true"  multiValued="true" required="false" />
> <dynamicField name="hierarchy.of.fields.*" type="text_en"
> indexed="true"  stored="true"  multiValued="true" required="false" />
>
>
> Or this case, I have a hierarchy where currently only one field should be
> captured "another.hierarchy.of.fields.Description", the rest for now should
> be just ignored. Is here any significance of which definition comes first?
>
> <dynamicField name="another.hierarchy.of.*" type="text_en"
> indexed="false"  stored="false"  multiValued="true" required="false" />
> <dynamicField name="another.hierarchy.of.fields.Description"
> type="text_en"    indexed="true"  stored="true"  multiValued="true"
> required="false" />
>
> Thanks for any hints,
> Tom