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 John Bickerstaff <jo...@johnbickerstaff.com> on 2016/08/04 19:37:14 UTC

Problems using fieldType text_general in copyField

Summary:

Using xinclude to include an xml file into schema.xml

The following line

<copyField source="content" dest="text"/>

generates an error:  about a field being "not a glob and not matching an
explicit field" even though I declare the field in the line just above.

This seems to happen only for for fieldType text_general?

============

Explanation:

I need a little help - keep getting an error when trying to use the ability
to include an additional XML file.  I may be overlooking something, but if
so, I need help to see it.

I have the following two lines which throw zero errors when part of
schema.xml:

<field name="content" type="text_general" indexed="false" stored="true"
multiValued="true"/>
 <copyField source="content" dest="text"/>

However, when I put this into an include file and use xinclude, then I get
this error when starting Solr.



   - *statdx_shard1_replica3:*
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
   Could not load conf for core statdx_shard1_replica3: Can't load schema
   schema.xml: copyField source :'content' is not a glob and doesn't match any
   explicit field or dynamicField.


Given that I am defining the field in the line right above the copyField
statement, I'm confused about why this works fine in schema.xml but NOT in
an included file.

I experimented and found that any field of type "text_general" will throw
this same error if it is part of the included xml file.  Other fieldTypes
that I tried (string, int, double) did not have this issue.

I'm using Solr 5.4, although I'm pulling custom config into an included
file for purposes of moving to 6.1

I have the following list of copyField commands in the included xml file,
and get no errors on any but the "content" one.  It just so happens that
"content" is the only field of type "text_general" in there.


Any hints greatly appreciated.

  <copyField source="title" dest="text"/>
   <copyField source="author" dest="text"/>
   <copyField source="description" dest="text"/>
   <copyField source="keywords" dest="text"/>
   <copyField source="content" dest="text"/>
   <copyField source="content_type" dest="text"/>
   <copyField source="resourcename" dest="text"/>
   <copyField source="url" dest="text"/>

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
I get the same error with the Entity Includes - with or without the
<schema> tag...

I'm probably just going to make a section in schema.xml rather than worry
about this.

Includes are "nice to have" but not critical.

On Thu, Aug 4, 2016 at 4:25 PM, John Bickerstaff <jo...@johnbickerstaff.com>
wrote:

> Found the Entity Includes - thanks.
>
> On Thu, Aug 4, 2016 at 4:22 PM, John Bickerstaff <john@johnbickerstaff.com
> > wrote:
>
>> Thanks!
>>
>> The schema is a copy of the techproducts sample.
>>
>> Entire include here - and I take your point about the possibility of
>> malformation - thanks.
>>
>> I assumed (perhaps wrongly) that I could duplicate the <schema ...>
>>  </schema> arrangement from the schema.xml file.
>>
>> I'm unfamiliar with xml entity includes, but I'll go look them up...
>>
>> <?xml version="1.0" encoding="UTF-8" ?>
>> <schema name="example" version="1.6">
>>
>>    <!-- ngram field to support suggestions / lookahead search on title
>> (and category, contentType)-->
>>    <copyField source="foobar" dest="text"/>
>>    <field name="suggestion_ngram_for_title" type="text_suggest_ngram"
>> indexed="true" stored="false"/>
>>    <field name="displayurl" type="text_general" indexed="true"
>> stored="true" multiValued="false"/>
>>    <field name="productVersionId" type="string" indexed="true"
>> stored="true" multiValued="false"/>
>>    <field name="caption" type="text_general" indexed="true" stored="true"
>> multiValued="false"/>
>>    <field name="documentId" type="string" indexed="true" stored="true"
>> multiValued="false"/>
>>    <!--<field name="category" type="string" indexed="true" stored="true"
>> multiValued="true"/>-->
>>    <field name="contentType" type="text_special_synonym" indexed="true"
>> stored="true" multiValued="false"/>
>>    <!-- Do NOT assume that much thought went into using int on the
>> following field. This is testing only!-->
>>    <field name="preference_" type="int" indexed="true" stored="true"
>> multiValued="false"/>
>>
>>    <field name="meta_doc_type" type="text_general" indexed="true"
>> stored="true" multiValued="false"/>
>>    <!--<field name="content" type="text_general" indexed="true"
>> stored="true" multiValued="false"/>-->
>>
>>    <!-- STATdx Weighting fields here. These are not part of the document,
>> but are used to calculate relevancy scores -->
>>    <field name="category_weight"  type="double" indexed="true"
>>  stored="true"/>    <!-- used for rule one - weighting docs on general
>> usefulness -->
>>
>>    <!-- Main body of document extracted by SolrCell.
>>         NOTE: This field is not indexed by default, since it is also
>> copied to "text"
>>         using copyField below. This is to save space. Use this field for
>> returning and
>>         highlighting document content. Use the "text" field to search the
>> content. -->
>>    <field name="content" type="text_en" indexed="false" stored="true"
>> multiValued="true"/> *//HERE IS WHERE "CONTENT" IS DEFINED*
>>
>> <!-- test for parsing statdx-provided html in content field. text_html
>> has been modified to clean html -->
>>    <field name="html_content" type="text_html" indexed="true"
>> stored="true" multiValued="true"/>
>>
>>    <!-- Text fields from SolrCell to search by default in our catch-all
>> field -->
>>    <copyField source="title" dest="text"/>
>>    <copyField source="author" dest="text"/>
>>    <copyField source="description" dest="text"/>
>>    <copyField source="keywords" dest="text"/>
>>    <copyField source="content" dest="text"/>  /*/THROWING ERROR ABOUT
>> "CONTENT" NOT EXISTING HERE*
>>    <copyField source="content_type" dest="text"/>
>>    <copyField source="resourcename" dest="text"/>
>>    <copyField source="url" dest="text"/>
>>
>>    <!-- Create a string version of author for faceting -->
>>    <copyField source="author" dest="author_s"/>
>>
>>   <!-- Above, multiple source fields are copied to the [text] field.
>>           Another way to map multiple source fields to the same
>>           destination field is to use the dynamic field syntax.
>>           copyField also supports a maxChars to copy setting.  -->
>>
>>         <copyField source="*_en" dest="text"/>
>>
>>
>>     <!-- a copy of text_general. Used to handle the rule that says that
>> docs with "table"
>>          and "tsm" in the contentType field should show at the top of
>> results IF any of the
>>          following terms are in the search term submitted by the user:
>>          [TNM, AJCC, Stage, Staging, FIGO]   Note the special synonym
>> file in the xml below.
>>          Note to self: Expand this documentation if we end up adding more
>> "special" synonyms -->
>>     <fieldType name="text_special_synonym" class="solr.TextField"
>> positionIncrementGap="100">
>>       <analyzer type="index">
>>         <tokenizer class="solr.StandardTokenizerFactory"/>
>>         <filter class="solr.StopFilterFactory" ignoreCase="true"
>> words="stopwords.txt" />
>>                 <!-- in this example, we will only use synonyms at query
>> time
>>         <filter class="solr.SynonymFilterFactory"
>> synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
>>         -->
>>         <filter class="solr.LowerCaseFilterFactory"/>
>>       </analyzer>
>>       <analyzer type="query">
>>         <tokenizer class="solr.StandardTokenizerFactory"/>
>>         <filter class="solr.StopFilterFactory" ignoreCase="true"
>> words="stopwords.txt" />
>>         <!-- Special synonym file here!!!!  -->
>>         <filter class="solr.SynonymFilterFactory"
>> synonyms="contentType_synonyms.txt" ignoreCase="true" expand="true"/>
>>         <filter class="solr.LowerCaseFilterFactory"/>
>>       </analyzer>
>>     </fieldType>
>>
>> </schema>
>>
>>
>>
>> On Thu, Aug 4, 2016 at 3:55 PM, Chris Hostetter <hossman_lucene@fucit.org
>> > wrote:
>>
>>>
>>> you mentioned that the problem only happens when you use xinclude, but
>>> you
>>> havne't shown us hte details of your xinclude -- what exactly does your
>>> schema.xml look like (with the xinclude call) and what exactly does the
>>> file being included look like (entire contents)
>>>
>>> (I suspect the problem you are seeing is realted to the way xinclude
>>> doens't really support "snippets" of malformed xml, and instead requires
>>> some root tag -- i can't imagine what root tag you are using in the
>>> included file that would play nicely with mixing/matching field
>>> declarations. ... using xml entity includes may be a simpler/safer
>>> option)
>>>
>>>
>>>
>>> : Date: Thu, 4 Aug 2016 15:47:00 -0600
>>> : From: John Bickerstaff <jo...@johnbickerstaff.com>
>>> : Reply-To: solr-user@lucene.apache.org
>>> : To: solr-user@lucene.apache.org
>>> : Subject: Re: Problems using fieldType text_general in copyField
>>> :
>>> : I would call this a bug...
>>> :
>>> : I'm going out on a limb and say that if you define a field in the
>>> included
>>> : XML file, you will get this error.
>>> :
>>> : As long as the field is defined first in schema.xml, you can
>>> "copyFIeld" it
>>> : or whatever in the include file, but apparently fields MUST be created
>>> in
>>> : the schema.xml file.
>>> :
>>> : That makes use of the include for custom things somewhat moot - at
>>> least in
>>> : my situation.
>>> :
>>> : I'd love to be wrong by the way, but that's what my tests suggest right
>>> : now...
>>> :
>>> : On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <
>>> john@johnbickerstaff.com>
>>> : wrote:
>>> :
>>> : > Summary:
>>> : >
>>> : > Using xinclude to include an xml file into schema.xml
>>> : >
>>> : > The following line
>>> : >
>>> : > <copyField source="content" dest="text"/>
>>> : >
>>> : > generates an error:  about a field being "not a glob and not
>>> matching an
>>> : > explicit field" even though I declare the field in the line just
>>> above.
>>> : >
>>> : > This seems to happen only for for fieldType text_general?
>>> : >
>>> : > ============
>>> : >
>>> : > Explanation:
>>> : >
>>> : > I need a little help - keep getting an error when trying to use the
>>> : > ability to include an additional XML file.  I may be overlooking
>>> something,
>>> : > but if so, I need help to see it.
>>> : >
>>> : > I have the following two lines which throw zero errors when part of
>>> : > schema.xml:
>>> : >
>>> : > <field name="content" type="text_general" indexed="false"
>>> stored="true"
>>> : > multiValued="true"/>
>>> : >  <copyField source="content" dest="text"/>
>>> : >
>>> : > However, when I put this into an include file and use xinclude, then
>>> I get
>>> : > this error when starting Solr.
>>> : >
>>> : >
>>> : >
>>> : >    - *statdx_shard1_replica3:* org.apache.solr.common.
>>> : >    SolrException:org.apache.solr.common.SolrException: Could not
>>> load
>>> : >    conf for core statdx_shard1_replica3: Can't load schema
>>> schema.xml:
>>> : >    copyField source :'content' is not a glob and doesn't match any
>>> explicit
>>> : >    field or dynamicField.
>>> : >
>>> : >
>>> : > Given that I am defining the field in the line right above the
>>> copyField
>>> : > statement, I'm confused about why this works fine in schema.xml but
>>> NOT in
>>> : > an included file.
>>> : >
>>> : > I experimented and found that any field of type "text_general" will
>>> throw
>>> : > this same error if it is part of the included xml file.  Other
>>> fieldTypes
>>> : > that I tried (string, int, double) did not have this issue.
>>> : >
>>> : > I'm using Solr 5.4, although I'm pulling custom config into an
>>> included
>>> : > file for purposes of moving to 6.1
>>> : >
>>> : > I have the following list of copyField commands in the included xml
>>> file,
>>> : > and get no errors on any but the "content" one.  It just so happens
>>> that
>>> : > "content" is the only field of type "text_general" in there.
>>> : >
>>> : >
>>> : > Any hints greatly appreciated.
>>> : >
>>> : >   <copyField source="title" dest="text"/>
>>> : >    <copyField source="author" dest="text"/>
>>> : >    <copyField source="description" dest="text"/>
>>> : >    <copyField source="keywords" dest="text"/>
>>> : >    <copyField source="content" dest="text"/>
>>> : >    <copyField source="content_type" dest="text"/>
>>> : >    <copyField source="resourcename" dest="text"/>
>>> : >    <copyField source="url" dest="text"/>
>>> : >
>>> : >
>>> :
>>>
>>> -Hoss
>>> http://www.lucidworks.com/
>>>
>>
>>
>

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
Found the Entity Includes - thanks.

On Thu, Aug 4, 2016 at 4:22 PM, John Bickerstaff <jo...@johnbickerstaff.com>
wrote:

> Thanks!
>
> The schema is a copy of the techproducts sample.
>
> Entire include here - and I take your point about the possibility of
> malformation - thanks.
>
> I assumed (perhaps wrongly) that I could duplicate the <schema ...>
>  </schema> arrangement from the schema.xml file.
>
> I'm unfamiliar with xml entity includes, but I'll go look them up...
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <schema name="example" version="1.6">
>
>    <!-- ngram field to support suggestions / lookahead search on title
> (and category, contentType)-->
>    <copyField source="foobar" dest="text"/>
>    <field name="suggestion_ngram_for_title" type="text_suggest_ngram"
> indexed="true" stored="false"/>
>    <field name="displayurl" type="text_general" indexed="true"
> stored="true" multiValued="false"/>
>    <field name="productVersionId" type="string" indexed="true"
> stored="true" multiValued="false"/>
>    <field name="caption" type="text_general" indexed="true" stored="true"
> multiValued="false"/>
>    <field name="documentId" type="string" indexed="true" stored="true"
> multiValued="false"/>
>    <!--<field name="category" type="string" indexed="true" stored="true"
> multiValued="true"/>-->
>    <field name="contentType" type="text_special_synonym" indexed="true"
> stored="true" multiValued="false"/>
>    <!-- Do NOT assume that much thought went into using int on the
> following field. This is testing only!-->
>    <field name="preference_" type="int" indexed="true" stored="true"
> multiValued="false"/>
>
>    <field name="meta_doc_type" type="text_general" indexed="true"
> stored="true" multiValued="false"/>
>    <!--<field name="content" type="text_general" indexed="true"
> stored="true" multiValued="false"/>-->
>
>    <!-- STATdx Weighting fields here. These are not part of the document,
> but are used to calculate relevancy scores -->
>    <field name="category_weight"  type="double" indexed="true"
>  stored="true"/>    <!-- used for rule one - weighting docs on general
> usefulness -->
>
>    <!-- Main body of document extracted by SolrCell.
>         NOTE: This field is not indexed by default, since it is also
> copied to "text"
>         using copyField below. This is to save space. Use this field for
> returning and
>         highlighting document content. Use the "text" field to search the
> content. -->
>    <field name="content" type="text_en" indexed="false" stored="true"
> multiValued="true"/> *//HERE IS WHERE "CONTENT" IS DEFINED*
>
> <!-- test for parsing statdx-provided html in content field. text_html has
> been modified to clean html -->
>    <field name="html_content" type="text_html" indexed="true"
> stored="true" multiValued="true"/>
>
>    <!-- Text fields from SolrCell to search by default in our catch-all
> field -->
>    <copyField source="title" dest="text"/>
>    <copyField source="author" dest="text"/>
>    <copyField source="description" dest="text"/>
>    <copyField source="keywords" dest="text"/>
>    <copyField source="content" dest="text"/>  /*/THROWING ERROR ABOUT
> "CONTENT" NOT EXISTING HERE*
>    <copyField source="content_type" dest="text"/>
>    <copyField source="resourcename" dest="text"/>
>    <copyField source="url" dest="text"/>
>
>    <!-- Create a string version of author for faceting -->
>    <copyField source="author" dest="author_s"/>
>
>   <!-- Above, multiple source fields are copied to the [text] field.
>           Another way to map multiple source fields to the same
>           destination field is to use the dynamic field syntax.
>           copyField also supports a maxChars to copy setting.  -->
>
>         <copyField source="*_en" dest="text"/>
>
>
>     <!-- a copy of text_general. Used to handle the rule that says that
> docs with "table"
>          and "tsm" in the contentType field should show at the top of
> results IF any of the
>          following terms are in the search term submitted by the user:
>          [TNM, AJCC, Stage, Staging, FIGO]   Note the special synonym file
> in the xml below.
>          Note to self: Expand this documentation if we end up adding more
> "special" synonyms -->
>     <fieldType name="text_special_synonym" class="solr.TextField"
> positionIncrementGap="100">
>       <analyzer type="index">
>         <tokenizer class="solr.StandardTokenizerFactory"/>
>         <filter class="solr.StopFilterFactory" ignoreCase="true"
> words="stopwords.txt" />
>                 <!-- in this example, we will only use synonyms at query
> time
>         <filter class="solr.SynonymFilterFactory"
> synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
>         -->
>         <filter class="solr.LowerCaseFilterFactory"/>
>       </analyzer>
>       <analyzer type="query">
>         <tokenizer class="solr.StandardTokenizerFactory"/>
>         <filter class="solr.StopFilterFactory" ignoreCase="true"
> words="stopwords.txt" />
>         <!-- Special synonym file here!!!!  -->
>         <filter class="solr.SynonymFilterFactory" synonyms="contentType_synonyms.txt"
> ignoreCase="true" expand="true"/>
>         <filter class="solr.LowerCaseFilterFactory"/>
>       </analyzer>
>     </fieldType>
>
> </schema>
>
>
>
> On Thu, Aug 4, 2016 at 3:55 PM, Chris Hostetter <ho...@fucit.org>
> wrote:
>
>>
>> you mentioned that the problem only happens when you use xinclude, but you
>> havne't shown us hte details of your xinclude -- what exactly does your
>> schema.xml look like (with the xinclude call) and what exactly does the
>> file being included look like (entire contents)
>>
>> (I suspect the problem you are seeing is realted to the way xinclude
>> doens't really support "snippets" of malformed xml, and instead requires
>> some root tag -- i can't imagine what root tag you are using in the
>> included file that would play nicely with mixing/matching field
>> declarations. ... using xml entity includes may be a simpler/safer option)
>>
>>
>>
>> : Date: Thu, 4 Aug 2016 15:47:00 -0600
>> : From: John Bickerstaff <jo...@johnbickerstaff.com>
>> : Reply-To: solr-user@lucene.apache.org
>> : To: solr-user@lucene.apache.org
>> : Subject: Re: Problems using fieldType text_general in copyField
>> :
>> : I would call this a bug...
>> :
>> : I'm going out on a limb and say that if you define a field in the
>> included
>> : XML file, you will get this error.
>> :
>> : As long as the field is defined first in schema.xml, you can
>> "copyFIeld" it
>> : or whatever in the include file, but apparently fields MUST be created
>> in
>> : the schema.xml file.
>> :
>> : That makes use of the include for custom things somewhat moot - at
>> least in
>> : my situation.
>> :
>> : I'd love to be wrong by the way, but that's what my tests suggest right
>> : now...
>> :
>> : On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <
>> john@johnbickerstaff.com>
>> : wrote:
>> :
>> : > Summary:
>> : >
>> : > Using xinclude to include an xml file into schema.xml
>> : >
>> : > The following line
>> : >
>> : > <copyField source="content" dest="text"/>
>> : >
>> : > generates an error:  about a field being "not a glob and not matching
>> an
>> : > explicit field" even though I declare the field in the line just
>> above.
>> : >
>> : > This seems to happen only for for fieldType text_general?
>> : >
>> : > ============
>> : >
>> : > Explanation:
>> : >
>> : > I need a little help - keep getting an error when trying to use the
>> : > ability to include an additional XML file.  I may be overlooking
>> something,
>> : > but if so, I need help to see it.
>> : >
>> : > I have the following two lines which throw zero errors when part of
>> : > schema.xml:
>> : >
>> : > <field name="content" type="text_general" indexed="false"
>> stored="true"
>> : > multiValued="true"/>
>> : >  <copyField source="content" dest="text"/>
>> : >
>> : > However, when I put this into an include file and use xinclude, then
>> I get
>> : > this error when starting Solr.
>> : >
>> : >
>> : >
>> : >    - *statdx_shard1_replica3:* org.apache.solr.common.
>> : >    SolrException:org.apache.solr.common.SolrException: Could not load
>> : >    conf for core statdx_shard1_replica3: Can't load schema schema.xml:
>> : >    copyField source :'content' is not a glob and doesn't match any
>> explicit
>> : >    field or dynamicField.
>> : >
>> : >
>> : > Given that I am defining the field in the line right above the
>> copyField
>> : > statement, I'm confused about why this works fine in schema.xml but
>> NOT in
>> : > an included file.
>> : >
>> : > I experimented and found that any field of type "text_general" will
>> throw
>> : > this same error if it is part of the included xml file.  Other
>> fieldTypes
>> : > that I tried (string, int, double) did not have this issue.
>> : >
>> : > I'm using Solr 5.4, although I'm pulling custom config into an
>> included
>> : > file for purposes of moving to 6.1
>> : >
>> : > I have the following list of copyField commands in the included xml
>> file,
>> : > and get no errors on any but the "content" one.  It just so happens
>> that
>> : > "content" is the only field of type "text_general" in there.
>> : >
>> : >
>> : > Any hints greatly appreciated.
>> : >
>> : >   <copyField source="title" dest="text"/>
>> : >    <copyField source="author" dest="text"/>
>> : >    <copyField source="description" dest="text"/>
>> : >    <copyField source="keywords" dest="text"/>
>> : >    <copyField source="content" dest="text"/>
>> : >    <copyField source="content_type" dest="text"/>
>> : >    <copyField source="resourcename" dest="text"/>
>> : >    <copyField source="url" dest="text"/>
>> : >
>> : >
>> :
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>
>

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
Many thanks for the assistance Hoss!  After a couple of bumps, it worked
great.

====

I followed the recommendations (and read the explanation - thanks!)

Although I swear it threw the error once again, just to be sure I rebooted
everything (Zookeeper included) then reloaded the configs into Zookeeper
and restarted my Solr servers - at that point the errors disappeared and
everything worked.

This will make upgrading super easy for us.  Given the relatively small
size of our data set, we have the luxury of just creating new Solr 6.1
instances in AWS, making a new node in Zookeeper, creating a collection,
adding the custom_schema file as you described and loading the data into
Solr from our Kafka store.  Gotta love it when your complete indexing into
Solr is in the neighborhood of two hours rather than two days or two weeks!

On Thu, Aug 4, 2016 at 8:42 PM, Alexandre Rafalovitch <ar...@gmail.com>
wrote:

> Just as a note, TYPO3 uses a lot of include files though I do not remember
> which specific mechanism they rely on.
>
> Regards,
>     Alex
>
> On 5 Aug 2016 10:51 AM, "John Bickerstaff" <jo...@johnbickerstaff.com>
> wrote:
>
> > Many thanks for your time!  Yes, it does make sense.
> >
> > I'll give your recommendation a shot tomorrow and update the thread.
> >
> > On Aug 4, 2016 6:22 PM, "Chris Hostetter" <ho...@fucit.org>
> > wrote:
> >
> >
> > TL;DR: use entity includes *WITH OUT TOP LEVEL WRAPPER ELEMENTS* like in
> > this example...
> >
> > https://github.com/apache/lucene-solr/blob/master/solr/
> > core/src/test-files/solr/collection1/conf/schema-snippet-types.incl
> > https://github.com/apache/lucene-solr/blob/master/solr/
> > core/src/test-files/solr/collection1/conf/schema-xinclude.xml
> >
> >
> > : The file I pasted last time is the file I was trying to include into
> the
> > : main schema.xml.  It was when that file was getting processed that I
> got
> > : the error  ['content' is not a glob and doesn't match any explicit
> field
> > or
> > : dynamicField. ]
> >
> > Ok -- so just to be crystal clear, you have two files, that look roughly
> > like this...
> >
> > --- BEGIN schema.xml ---
> > <?xml version="1.0" encoding="UTF-8" ?>
> > <schema name="statdx" version="1.5">
> >   <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
> >     -->
> >   <xi:include href="statdx_custom_schema.xml" xmlns:xi="
> http://www.w3.org/
> > 2001/XInclude"/>
> > </schema>
> > --- END schema.xml ---
> >
> > -- BEGIN statdx_custom_schema.xml ---
> > <?xml version="1.0" encoding="UTF-8" ?>
> > <schema name="example" version="1.6">
> >   <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
> >        declarations
> >     -->
> > </schema>
> > --- END statdx_custom_schema.xml ---
> >
> > ...am I correct?
> >
> >
> > I'm going to skip a lot of the nitty gritty and just summarize by saying
> > that ultimately there are 2 problems here that combine to lead to the
> > error you are getting:
> >
> > 1) what you are trying to do as far as the xinclude is not really what
> > xinclude is designed for and doesn't work the way you (or any other sane
> > person) would think it does.
> >
> > 2) for historical reasons, Solr is being sloppy in what <copyField>
> > entries it recognizes.  If anything the "bug" is that Solr is
> > willing to try to load any parts of your include file at all -- it it
> were
> > behaving consistently it should be ignoring all of it.
> >
> >
> > Ok ... that seems terse, i'll clarify with a little of the nitty
> gritty...
> >
> >
> > The root of the issue is really something you alluded to earlier that
> > dind't make sense to me at the time because I didn't realize you were
> > showing us the *includED* file when you said it...
> >
> > >>> I assumed (perhaps wrongly) that I could duplicate the <schema ...>
> > >>>  </schema> arrangement from the schema.xml file.
> >
> > ...that assumption is the crux of the problem, because when the XML
> parser
> > evaluates your xinclude, what it produces is functionally equivilent to
> if
> > you had a schema.xml file that looked like this....
> >
> > --- BEGIN EFFECTIVE schema.xml ---
> > <?xml version="1.0" encoding="UTF-8" ?>
> > <schema name="statdx" version="1.5">
> >   <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
> >     -->
> >   <schema name="example" version="1.6">
> >     <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
> >          declarations
> >       -->
> >   </schema>
> > </schema>
> > --- END EFFECTIVE schema.xml ---
> >
> > ...that extra <schema> element nested inside of the original <schema>
> > element is what's confusing the hell out of solr.  The <field> and
> > <fieldType> parsing is fairly strict, and only expects to find them as
> top
> > level elements (or, for historical purposes, as children of <fields> and
> > <types> -- note the plurals) while the <copyField> parsing is sloppy and
> > finds the one that gives you an error.
> >
> > (Even if the <field> and <fieldType> parsing was equally sloppy, only the
> > outermost <schema> tag would be recognized, so your default field props
> > would be based on the version="1.5" declaration, not the version="1.6"
> > declaration of the included file they'd be in ... which would be
> confusing
> > as hell, so it's a good thing Solr isn't sloppy about that parsing too)
> >
> >
> > In contrast to xincludes, XML Entity includes are (almost as a side
> effect
> > of the triviality of their design) vastly supperiour 90% of the time, and
> > capable of doing what you want.  The key diff being that Entity includes
> > do not require that the file being included is valid XML -- it can be an
> > arbitrary snippet of xml content (w/o a top level element) that will be
> > inlined verbatim.  so you can/should do soemthing like this...
> >
> > --- BEGIN schema.xml ---
> > <?xml version="1.0" encoding="UTF-8" ?>
> > <!DOCTYPE schema [
> >     <!ENTITY statdx_custom_include SYSTEM "statdx_custom_schema.incl">
> >     ]>
> > <schema name="statdx" version="1.5">
> >   <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
> >     -->
> >   &statdx_custom_include;
> > </schema>
> > --- END schema.xml ---
> >
> > -- BEGIN statdx_custom_schema.incl ---
> > <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
> >      declarations
> >   -->
> > --- END statdx_custom_schema.incl ---
> >
> >
> > ...make sense?
> >
> >
> > -Hoss
> > http://www.lucidworks.com/
> >
>

Re: Problems using fieldType text_general in copyField

Posted by Alexandre Rafalovitch <ar...@gmail.com>.
Just as a note, TYPO3 uses a lot of include files though I do not remember
which specific mechanism they rely on.

Regards,
    Alex

On 5 Aug 2016 10:51 AM, "John Bickerstaff" <jo...@johnbickerstaff.com> wrote:

> Many thanks for your time!  Yes, it does make sense.
>
> I'll give your recommendation a shot tomorrow and update the thread.
>
> On Aug 4, 2016 6:22 PM, "Chris Hostetter" <ho...@fucit.org>
> wrote:
>
>
> TL;DR: use entity includes *WITH OUT TOP LEVEL WRAPPER ELEMENTS* like in
> this example...
>
> https://github.com/apache/lucene-solr/blob/master/solr/
> core/src/test-files/solr/collection1/conf/schema-snippet-types.incl
> https://github.com/apache/lucene-solr/blob/master/solr/
> core/src/test-files/solr/collection1/conf/schema-xinclude.xml
>
>
> : The file I pasted last time is the file I was trying to include into the
> : main schema.xml.  It was when that file was getting processed that I got
> : the error  ['content' is not a glob and doesn't match any explicit field
> or
> : dynamicField. ]
>
> Ok -- so just to be crystal clear, you have two files, that look roughly
> like this...
>
> --- BEGIN schema.xml ---
> <?xml version="1.0" encoding="UTF-8" ?>
> <schema name="statdx" version="1.5">
>   <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
>     -->
>   <xi:include href="statdx_custom_schema.xml" xmlns:xi="http://www.w3.org/
> 2001/XInclude"/>
> </schema>
> --- END schema.xml ---
>
> -- BEGIN statdx_custom_schema.xml ---
> <?xml version="1.0" encoding="UTF-8" ?>
> <schema name="example" version="1.6">
>   <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
>        declarations
>     -->
> </schema>
> --- END statdx_custom_schema.xml ---
>
> ...am I correct?
>
>
> I'm going to skip a lot of the nitty gritty and just summarize by saying
> that ultimately there are 2 problems here that combine to lead to the
> error you are getting:
>
> 1) what you are trying to do as far as the xinclude is not really what
> xinclude is designed for and doesn't work the way you (or any other sane
> person) would think it does.
>
> 2) for historical reasons, Solr is being sloppy in what <copyField>
> entries it recognizes.  If anything the "bug" is that Solr is
> willing to try to load any parts of your include file at all -- it it were
> behaving consistently it should be ignoring all of it.
>
>
> Ok ... that seems terse, i'll clarify with a little of the nitty gritty...
>
>
> The root of the issue is really something you alluded to earlier that
> dind't make sense to me at the time because I didn't realize you were
> showing us the *includED* file when you said it...
>
> >>> I assumed (perhaps wrongly) that I could duplicate the <schema ...>
> >>>  </schema> arrangement from the schema.xml file.
>
> ...that assumption is the crux of the problem, because when the XML parser
> evaluates your xinclude, what it produces is functionally equivilent to if
> you had a schema.xml file that looked like this....
>
> --- BEGIN EFFECTIVE schema.xml ---
> <?xml version="1.0" encoding="UTF-8" ?>
> <schema name="statdx" version="1.5">
>   <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
>     -->
>   <schema name="example" version="1.6">
>     <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
>          declarations
>       -->
>   </schema>
> </schema>
> --- END EFFECTIVE schema.xml ---
>
> ...that extra <schema> element nested inside of the original <schema>
> element is what's confusing the hell out of solr.  The <field> and
> <fieldType> parsing is fairly strict, and only expects to find them as top
> level elements (or, for historical purposes, as children of <fields> and
> <types> -- note the plurals) while the <copyField> parsing is sloppy and
> finds the one that gives you an error.
>
> (Even if the <field> and <fieldType> parsing was equally sloppy, only the
> outermost <schema> tag would be recognized, so your default field props
> would be based on the version="1.5" declaration, not the version="1.6"
> declaration of the included file they'd be in ... which would be confusing
> as hell, so it's a good thing Solr isn't sloppy about that parsing too)
>
>
> In contrast to xincludes, XML Entity includes are (almost as a side effect
> of the triviality of their design) vastly supperiour 90% of the time, and
> capable of doing what you want.  The key diff being that Entity includes
> do not require that the file being included is valid XML -- it can be an
> arbitrary snippet of xml content (w/o a top level element) that will be
> inlined verbatim.  so you can/should do soemthing like this...
>
> --- BEGIN schema.xml ---
> <?xml version="1.0" encoding="UTF-8" ?>
> <!DOCTYPE schema [
>     <!ENTITY statdx_custom_include SYSTEM "statdx_custom_schema.incl">
>     ]>
> <schema name="statdx" version="1.5">
>   <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
>     -->
>   &statdx_custom_include;
> </schema>
> --- END schema.xml ---
>
> -- BEGIN statdx_custom_schema.incl ---
> <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
>      declarations
>   -->
> --- END statdx_custom_schema.incl ---
>
>
> ...make sense?
>
>
> -Hoss
> http://www.lucidworks.com/
>

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
Many thanks for your time!  Yes, it does make sense.

I'll give your recommendation a shot tomorrow and update the thread.

On Aug 4, 2016 6:22 PM, "Chris Hostetter" <ho...@fucit.org> wrote:


TL;DR: use entity includes *WITH OUT TOP LEVEL WRAPPER ELEMENTS* like in
this example...

https://github.com/apache/lucene-solr/blob/master/solr/
core/src/test-files/solr/collection1/conf/schema-snippet-types.incl
https://github.com/apache/lucene-solr/blob/master/solr/
core/src/test-files/solr/collection1/conf/schema-xinclude.xml


: The file I pasted last time is the file I was trying to include into the
: main schema.xml.  It was when that file was getting processed that I got
: the error  ['content' is not a glob and doesn't match any explicit field
or
: dynamicField. ]

Ok -- so just to be crystal clear, you have two files, that look roughly
like this...

--- BEGIN schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<schema name="statdx" version="1.5">
  <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
    -->
  <xi:include href="statdx_custom_schema.xml" xmlns:xi="http://www.w3.org/
2001/XInclude"/>
</schema>
--- END schema.xml ---

-- BEGIN statdx_custom_schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<schema name="example" version="1.6">
  <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
       declarations
    -->
</schema>
--- END statdx_custom_schema.xml ---

...am I correct?


I'm going to skip a lot of the nitty gritty and just summarize by saying
that ultimately there are 2 problems here that combine to lead to the
error you are getting:

1) what you are trying to do as far as the xinclude is not really what
xinclude is designed for and doesn't work the way you (or any other sane
person) would think it does.

2) for historical reasons, Solr is being sloppy in what <copyField>
entries it recognizes.  If anything the "bug" is that Solr is
willing to try to load any parts of your include file at all -- it it were
behaving consistently it should be ignoring all of it.


Ok ... that seems terse, i'll clarify with a little of the nitty gritty...


The root of the issue is really something you alluded to earlier that
dind't make sense to me at the time because I didn't realize you were
showing us the *includED* file when you said it...

>>> I assumed (perhaps wrongly) that I could duplicate the <schema ...>
>>>  </schema> arrangement from the schema.xml file.

...that assumption is the crux of the problem, because when the XML parser
evaluates your xinclude, what it produces is functionally equivilent to if
you had a schema.xml file that looked like this....

--- BEGIN EFFECTIVE schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<schema name="statdx" version="1.5">
  <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
    -->
  <schema name="example" version="1.6">
    <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
         declarations
      -->
  </schema>
</schema>
--- END EFFECTIVE schema.xml ---

...that extra <schema> element nested inside of the original <schema>
element is what's confusing the hell out of solr.  The <field> and
<fieldType> parsing is fairly strict, and only expects to find them as top
level elements (or, for historical purposes, as children of <fields> and
<types> -- note the plurals) while the <copyField> parsing is sloppy and
finds the one that gives you an error.

(Even if the <field> and <fieldType> parsing was equally sloppy, only the
outermost <schema> tag would be recognized, so your default field props
would be based on the version="1.5" declaration, not the version="1.6"
declaration of the included file they'd be in ... which would be confusing
as hell, so it's a good thing Solr isn't sloppy about that parsing too)


In contrast to xincludes, XML Entity includes are (almost as a side effect
of the triviality of their design) vastly supperiour 90% of the time, and
capable of doing what you want.  The key diff being that Entity includes
do not require that the file being included is valid XML -- it can be an
arbitrary snippet of xml content (w/o a top level element) that will be
inlined verbatim.  so you can/should do soemthing like this...

--- BEGIN schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE schema [
    <!ENTITY statdx_custom_include SYSTEM "statdx_custom_schema.incl">
    ]>
<schema name="statdx" version="1.5">
  <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
    -->
  &statdx_custom_include;
</schema>
--- END schema.xml ---

-- BEGIN statdx_custom_schema.incl ---
<!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField>
     declarations
  -->
--- END statdx_custom_schema.incl ---


...make sense?


-Hoss
http://www.lucidworks.com/

Re: Problems using fieldType text_general in copyField

Posted by Chris Hostetter <ho...@fucit.org>.
TL;DR: use entity includes *WITH OUT TOP LEVEL WRAPPER ELEMENTS* like in 
this example...

https://github.com/apache/lucene-solr/blob/master/solr/core/src/test-files/solr/collection1/conf/schema-snippet-types.incl
https://github.com/apache/lucene-solr/blob/master/solr/core/src/test-files/solr/collection1/conf/schema-xinclude.xml


: The file I pasted last time is the file I was trying to include into the
: main schema.xml.  It was when that file was getting processed that I got
: the error  ['content' is not a glob and doesn't match any explicit field or
: dynamicField. ]

Ok -- so just to be crystal clear, you have two files, that look roughly 
like this...

--- BEGIN schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<schema name="statdx" version="1.5">
  <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
    -->
  <xi:include href="statdx_custom_schema.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
</schema>
--- END schema.xml ---

-- BEGIN statdx_custom_schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<schema name="example" version="1.6">
  <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField> 
       declarations
    -->
</schema>
--- END statdx_custom_schema.xml ---

...am I correct?


I'm going to skip a lot of the nitty gritty and just summarize by saying 
that ultimately there are 2 problems here that combine to lead to the 
error you are getting:

1) what you are trying to do as far as the xinclude is not really what 
xinclude is designed for and doesn't work the way you (or any other sane 
person) would think it does.

2) for historical reasons, Solr is being sloppy in what <copyField> 
entries it recognizes.  If anything the "bug" is that Solr is 
willing to try to load any parts of your include file at all -- it it were 
behaving consistently it should be ignoring all of it.


Ok ... that seems terse, i'll clarify with a little of the nitty gritty...


The root of the issue is really something you alluded to earlier that 
dind't make sense to me at the time because I didn't realize you were 
showing us the *includED* file when you said it...

>>> I assumed (perhaps wrongly) that I could duplicate the <schema ...>
>>>  </schema> arrangement from the schema.xml file.

...that assumption is the crux of the problem, because when the XML parser 
evaluates your xinclude, what it produces is functionally equivilent to if 
you had a schema.xml file that looked like this....

--- BEGIN EFFECTIVE schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<schema name="statdx" version="1.5">
  <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
    -->
  <schema name="example" version="1.6">
    <!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField> 
         declarations
      -->
  </schema>
</schema>
--- END EFFECTIVE schema.xml ---

...that extra <schema> element nested inside of the original <schema> 
element is what's confusing the hell out of solr.  The <field> and 
<fieldType> parsing is fairly strict, and only expects to find them as top 
level elements (or, for historical purposes, as children of <fields> and 
<types> -- note the plurals) while the <copyField> parsing is sloppy and 
finds the one that gives you an error.

(Even if the <field> and <fieldType> parsing was equally sloppy, only the 
outermost <schema> tag would be recognized, so your default field props 
would be based on the version="1.5" declaration, not the version="1.6" 
declaration of the included file they'd be in ... which would be confusing 
as hell, so it's a good thing Solr isn't sloppy about that parsing too)


In contrast to xincludes, XML Entity includes are (almost as a side effect 
of the triviality of their design) vastly supperiour 90% of the time, and 
capable of doing what you want.  The key diff being that Entity includes 
do not require that the file being included is valid XML -- it can be an 
arbitrary snippet of xml content (w/o a top level element) that will be 
inlined verbatim.  so you can/should do soemthing like this...

--- BEGIN schema.xml ---
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE schema [
    <!ENTITY statdx_custom_include SYSTEM "statdx_custom_schema.incl">
    ]>
<schema name="statdx" version="1.5">
  <!-- a whole lot of <field>, <fieldType>, and <copyField> declarations
    -->
  &statdx_custom_include;
</schema>
--- END schema.xml ---

-- BEGIN statdx_custom_schema.incl ---
<!-- a whole lot of ADDITIONAL <field>, <fieldType>, and <copyField> 
     declarations
  -->
--- END statdx_custom_schema.incl ---


...make sense?


-Hoss
http://www.lucidworks.com/

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
Thanks and sorry for the misunderstanding.

The file I pasted last time is the file I was trying to include into the
main schema.xml.  It was when that file was getting processed that I got
the error  ['content' is not a glob and doesn't match any explicit field or
dynamicField. ]

I should note that I tried this with and without the <schema> tags and got
the same error both times.

I used this line inside the main schema.xml to include the one I pasted in
the last email.

<xi:include href="statdx_custom_schema.xml" xmlns:xi="
http://www.w3.org/2001/XInclude"/>

What follows is my main schema.xml which was  an exact copy of the
schema.xml that ships with Solr in the techproducts sample.

At the very bottom of the text / file, you'll see the line I used to
include the "statdx_custom_schema.xml" file

======


<?xml version="1.0" encoding="UTF-8" ?>

<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
-->

<!--
 This is the Solr schema file. This file should be named "schema.xml" and
 should be in the conf directory under the solr home
 (i.e. ./solr/conf/schema.xml by default)
 or located where the classloader for the Solr webapp can find it.

 This example schema is the recommended starting point for users.
 It should be kept correct and concise, usable out-of-the-box.

 For more information, on how to customize this file, please see
 http://wiki.apache.org/solr/SchemaXml

 PERFORMANCE NOTE: this schema includes many optional features and should
not
 be used for benchmarking.  To improve performance one could
  - set stored="false" for all fields possible (esp large fields) when you
    only need to search on the field but don't need to return the original
    value.
  - set indexed="false" if you don't need to search on the field, but only
    return the field as a result of searching on other indexed fields.
  - remove all unneeded copyField statements
  - for best index size and searching performance, set "index" to false
    for all general text fields, use copyField to copy them to the
    catchall "text" field, and use that for searching.
  - For maximum indexing performance, use the ConcurrentUpdateSolrServer
    java client.
  - Remember to run the JVM in server mode, and use a higher logging level
    that avoids logging every request
-->

<schema name="statdx" version="1.5">

  <!-- attribute "name" is the name of this schema and is only used for
display purposes.
       version="x.y" is Solr's version number for the schema syntax and
       semantics.  It should not normally be changed by applications.

       1.0: multiValued attribute did not exist, all fields are multiValued
            by nature
       1.1: multiValued attribute introduced, false by default
       1.2: omitTermFreqAndPositions attribute introduced, true by default
            except for text fields.
       1.3: removed optional field compress feature
       1.4: autoGeneratePhraseQueries attribute introduced to drive
QueryParser
            behavior when a single string produces multiple tokens.
Defaults
            to off for version >= 1.4
       1.5: omitNorms defaults to true for primitive field types
            (int, float, boolean, string...)
     -->


   <!-- Valid attributes for fields:
     name: mandatory - the name for the field
     type: mandatory - the name of a field type from the
       <types> fieldType section
     indexed: true if this field should be indexed (searchable or sortable)
     stored: true if this field should be retrievable
     docValues: true if this field should have doc values. Doc values are
       useful for faceting, grouping, sorting and function queries.
Although not
       required, doc values will make the index faster to load, more
       NRT-friendly and more memory-efficient. They however come with some
       limitations: they are currently only supported by StrField, UUIDField
       and all Trie*Fields, and depending on the field type, they might
       require the field to be single-valued, be required or have a default
       value (check the documentation of the field type you're interested in
       for more information)
     multiValued: true if this field may contain multiple values per
document
     omitNorms: (expert) set to true to omit the norms associated with
       this field (this disables length normalization and index-time
       boosting for the field, and saves some memory).  Only full-text
       fields or fields that need an index-time boost need norms.
       Norms are omitted for primitive (non-analyzed) types by default.
     termVectors: [false] set to true to store the term vector for a
       given field.
       When using MoreLikeThis, fields used for similarity should be
       stored for best performance.
     termPositions: Store position information with the term vector.
       This will increase storage costs.
     termOffsets: Store offset information with the term vector. This
       will increase storage costs.
     required: The field is required.  It will throw an error if the
       value does not exist
     default: a value that should be used if no value is specified
       when adding a document.
   -->

   <!-- field names should consist of alphanumeric or underscore characters
only and
      not start with a digit.  This is not currently strictly enforced,
      but other field names will not have first class support from all
components
      and back compatibility is not guaranteed.  Names with both leading and
      trailing underscores (e.g. _version_) are reserved.
   -->

   <!-- If you remove this field, you must _also_ disable the update log in
solrconfig.xml
      or Solr won't start. _version_ and update log are required for
SolrCloud
   -->
   <field name="_version_" type="long" indexed="true" stored="true"/>

   <!-- points to the root document of a block of nested documents.
Required for nested
      document support, may be removed otherwise
   -->
   <field name="_root_" type="string" indexed="true" stored="false"/>

   <!-- Only remove the "id" field if you have a very good reason to. While
not strictly
     required, it is highly recommended. A <uniqueKey> is present in almost
all Solr
     installations. See the <uniqueKey> declaration below where <uniqueKey>
is set to "id".
   -->
   <field name="id" type="string" indexed="true" stored="true"
required="true" multiValued="false" />

   <field name="sku" type="text_en_splitting_tight" indexed="true"
stored="true" omitNorms="true"/>
   <field name="name" type="text_general" indexed="true" stored="true"/>
   <field name="manu" type="text_general" indexed="true" stored="true"
omitNorms="true"/>
   <field name="cat" type="string" indexed="true" stored="true"
multiValued="true"/>
   <field name="features" type="text_general" indexed="true" stored="true"
multiValued="true"/>
   <field name="includes" type="text_general" indexed="true" stored="true"
termVectors="true" termPositions="true" termOffsets="true" />

   <field name="weight" type="float" indexed="true" stored="true"/>
   <field name="price"  type="float" indexed="true" stored="true"/>
   <field name="popularity" type="int" indexed="true" stored="true" />
   <field name="inStock" type="boolean" indexed="true" stored="true" />

   <field name="store" type="location" indexed="true" stored="true"/>

   <!-- Common metadata fields, named specifically to match up with
     SolrCell metadata when parsing rich documents such as Word, PDF.
     Some fields are multiValued only because Tika currently may return
     multiple values for them. Some metadata is parsed from the documents,
     but there are some which come from the client context:
       "content_type": From the HTTP headers of incoming stream
       "resourcename": From SolrCell request param resource.name
   -->
   <field name="title" type="text_general" indexed="true" stored="true"
multiValued="true"/>
   <field name="subject" type="text_general" indexed="true" stored="true"/>
   <field name="description" type="text_general" indexed="true"
stored="true"/>
   <field name="comments" type="text_general" indexed="true" stored="true"/>
   <field name="author" type="text_general" indexed="true" stored="true"/>
   <field name="keywords" type="text_general" indexed="true" stored="true"/>
   <field name="category" type="text_general" indexed="true" stored="true"/>
   <field name="resourcename" type="text_general" indexed="true"
stored="true"/>
   <field name="url" type="text_general" indexed="true" stored="true"/>
   <field name="content_type" type="string" indexed="true" stored="true"
multiValued="true"/>
   <field name="last_modified" type="date" indexed="true" stored="true"/>
   <field name="links" type="string" indexed="true" stored="true"
multiValued="true"/>


   <!-- catchall field, containing all other searchable text fields
(implemented
        via copyField further on in this schema  -->
   <field name="text" type="text_general" indexed="true" stored="false"
multiValued="true"/>

   <!-- catchall text field that indexes tokens both normally and in
reverse for efficient
        leading wildcard queries. -->
   <field name="text_rev" type="text_general_rev" indexed="true"
stored="false" multiValued="true"/>

   <!-- non-tokenized version of manufacturer to make it easier to sort or
group
        results by manufacturer.  copied from "manu" via copyField -->
   <field name="manu_exact" type="string" indexed="true" stored="false"/>

   <field name="payloads" type="payloads" indexed="true" stored="true"/>


   <!--
     Some fields such as popularity and manu_exact could be modified to
     leverage doc values:
     <field name="popularity" type="int" indexed="true" stored="true"
docValues="true" />
     <field name="manu_exact" type="string" indexed="false" stored="false"
docValues="true" />
     <field name="cat" type="string" indexed="true" stored="true"
docValues="true" multiValued="true"/>


     Although it would make indexing slightly slower and the index bigger,
it
     would also make the index faster to load, more memory-efficient and
more
     NRT-friendly.
     -->

   <!-- Dynamic field definitions allow using convention over configuration
       for fields via the specification of patterns to match field names.
       EXAMPLE:  name="*_i" will match any field ending in _i (like myid_i,
z_i)
       RESTRICTION: the glob-like pattern in the name attribute must have
       a "*" only at the start or the end.  -->

   <dynamicField name="*_i"  type="int"    indexed="true"  stored="true"/>
   <dynamicField name="*_is" type="int"    indexed="true"  stored="true"
 multiValued="true"/>
   <dynamicField name="*_s"  type="string"  indexed="true"  stored="true" />
   <dynamicField name="*_ss" type="string"  indexed="true"  stored="true"
multiValued="true"/>
   <dynamicField name="*_l"  type="long"   indexed="true"  stored="true"/>
   <dynamicField name="*_ls" type="long"   indexed="true"  stored="true"
 multiValued="true"/>
   <dynamicField name="*_t"  type="text_general"    indexed="true"
 stored="true"/>
   <dynamicField name="*_txt" type="text_general"   indexed="true"
 stored="true" multiValued="true"/>
   <dynamicField name="*_en"  type="text_en"    indexed="true"
 stored="true" multiValued="true"/>
   <dynamicField name="*_b"  type="boolean" indexed="true" stored="true"/>
   <dynamicField name="*_bs" type="boolean" indexed="true" stored="true"
 multiValued="true"/>
   <dynamicField name="*_f"  type="float"  indexed="true"  stored="true"/>
   <dynamicField name="*_fs" type="float"  indexed="true"  stored="true"
 multiValued="true"/>
   <dynamicField name="*_d"  type="double" indexed="true"  stored="true"/>
   <dynamicField name="*_ds" type="double" indexed="true"  stored="true"
 multiValued="true"/>

   <!-- Type used to index the lat and lon components for the "location"
FieldType -->
   <dynamicField name="*_coordinate"  type="tdouble" indexed="true"
 stored="false" />

   <dynamicField name="*_dt"  type="date"    indexed="true"  stored="true"/>
   <dynamicField name="*_dts" type="date"    indexed="true"  stored="true"
multiValued="true"/>
   <dynamicField name="*_p"  type="location" indexed="true" stored="true"/>

   <!-- some trie-coded dynamic fields for faster range queries -->
   <dynamicField name="*_ti" type="tint"    indexed="true"  stored="true"/>
   <dynamicField name="*_tl" type="tlong"   indexed="true"  stored="true"/>
   <dynamicField name="*_tf" type="tfloat"  indexed="true"  stored="true"/>
   <dynamicField name="*_td" type="tdouble" indexed="true"  stored="true"/>
   <dynamicField name="*_tdt" type="tdate"  indexed="true"  stored="true"/>

   <dynamicField name="*_c"   type="currency" indexed="true"
 stored="true"/>

   <dynamicField name="ignored_*" type="ignored" multiValued="true"/>
   <dynamicField name="attr_*" type="text_general" indexed="true"
stored="true" multiValued="true"/>

   <dynamicField name="random_*" type="random" />

   <!-- uncomment the following to ignore any fields that don't already
match an existing
        field name or dynamic field, rather than reporting them as an
error.
        alternately, change the type="ignored" to some other type e.g.
"text" if you want
        unknown fields indexed and/or stored by default -->
   <!--dynamicField name="*" type="ignored" multiValued="true" /-->




 <!-- Field to use to determine and enforce document uniqueness.
      Unless this field is marked with required="false", it will be a
required field
   -->
 <uniqueKey>id</uniqueKey>

 <!-- DEPRECATED: The defaultSearchField is consulted by various query
parsers when
  parsing a query string that isn't explicit about the field.  Machine
(non-user)
  generated queries are best made explicit, or they can use the "df"
request parameter
  which takes precedence over this.
  Note: Un-commenting defaultSearchField will be insufficient if your
request handler
  in solrconfig.xml defines "df", which takes precedence. That would need
to be removed.
 <defaultSearchField>text</defaultSearchField> -->

 <!-- DEPRECATED: The defaultOperator (AND|OR) is consulted by various
query parsers
  when parsing a query string to determine if a clause of the query should
be marked as
  required or optional, assuming the clause isn't already marked by some
operator.
  The default is OR, which is generally assumed so it is not a good idea to
change it
  globally here.  The "q.op" request parameter takes precedence over this.
 <solrQueryParser defaultOperator="OR"/> -->

  <!-- copyField commands copy one field to another at the time a document
        is added to the index.  It's used either to index the same field
differently,
        or to add multiple fields to the same field for easier/faster
searching.  -->

   <copyField source="cat" dest="text"/>
   <copyField source="name" dest="text"/>
   <copyField source="manu" dest="text"/>
   <copyField source="features" dest="text"/>
   <copyField source="includes" dest="text"/>
   <copyField source="manu" dest="manu_exact"/>

   <!-- Copy the price into a currency enabled field (default USD) -->
   <copyField source="price" dest="price_c"/>

   <!-- Above, multiple source fields are copied to the [text] field.
 Another way to map multiple source fields to the same
 destination field is to use the dynamic field syntax.
 copyField also supports a maxChars to copy setting.  -->

   <!-- <copyField source="*_t" dest="text" maxChars="3000"/> -->

   <!-- copy name to alphaNameSort, a field designed for sorting by name -->
   <!-- <copyField source="name" dest="alphaNameSort"/> -->


    <!-- field type definitions. The "name" attribute is
       just a label to be used by field definitions.  The "class"
       attribute and any other attributes determine the real
       behavior of the fieldType.
         Class names starting with "solr" refer to java classes in a
       standard package such as org.apache.solr.analysis
    -->


<!-- statdx statdx statdx -->



    <!-- The StrField type is not analyzed, but indexed/stored verbatim.
       It supports doc values but in that case the field needs to be
       single-valued and either required or have a default value.
      -->
    <fieldType name="string" class="solr.StrField" sortMissingLast="true" />

    <!-- boolean type: "true" or "false" -->
    <fieldType name="boolean" class="solr.BoolField"
sortMissingLast="true"/>

    <!-- sortMissingLast and sortMissingFirst attributes are optional
attributes are
         currently supported on types that are sorted internally as strings
         and on numeric types.
    This includes "string","boolean", and, as of 3.5 (and 4.x),
    int, float, long, date, double, including the "Trie" variants.
       - If sortMissingLast="true", then a sort on this field will cause
documents
         without the field to come after documents with the field,
         regardless of the requested sort order (asc or desc).
       - If sortMissingFirst="true", then a sort on this field will cause
documents
         without the field to come before documents with the field,
         regardless of the requested sort order.
       - If sortMissingLast="false" and sortMissingFirst="false" (the
default),
         then default lucene sorting will be used which places docs without
the
         field first in an ascending sort and last in a descending sort.
    -->

    <!--
      Default numeric field types. For faster range queries, consider the
tint/tfloat/tlong/tdouble types.

      These fields support doc values, but they require the field to be
      single-valued and either be required or have a default value.
    -->
    <fieldType name="int" class="solr.TrieIntField" precisionStep="0"
positionIncrementGap="0"/>
    <fieldType name="float" class="solr.TrieFloatField" precisionStep="0"
positionIncrementGap="0"/>
    <fieldType name="long" class="solr.TrieLongField" precisionStep="0"
positionIncrementGap="0"/>
    <fieldType name="double" class="solr.TrieDoubleField" precisionStep="0"
positionIncrementGap="0"/>

    <!--
     Numeric field types that index each value at various levels of
precision
     to accelerate range queries when the number of values between the range
     endpoints is large. See the javadoc for NumericRangeQuery for internal
     implementation details.

     Smaller precisionStep values (specified in bits) will lead to more
tokens
     indexed per value, slightly larger index size, and faster range
queries.
     A precisionStep of 0 disables indexing at different precision levels.
    -->
    <fieldType name="tint" class="solr.TrieIntField" precisionStep="8"
positionIncrementGap="0"/>
    <fieldType name="tfloat" class="solr.TrieFloatField" precisionStep="8"
positionIncrementGap="0"/>
    <fieldType name="tlong" class="solr.TrieLongField" precisionStep="8"
positionIncrementGap="0"/>
    <fieldType name="tdouble" class="solr.TrieDoubleField"
precisionStep="8" positionIncrementGap="0"/>

    <!-- The format for this date field is of the form
1995-12-31T23:59:59Z, and
         is a more restricted form of the canonical representation of
dateTime
         http://www.w3.org/TR/xmlschema-2/#dateTime
         The trailing "Z" designates UTC time and is mandatory.
         Optional fractional seconds are allowed: 1995-12-31T23:59:59.999Z
         All other components are mandatory.

         Expressions can also be used to denote calculations that should be
         performed relative to "NOW" to determine the value, ie...

               NOW/HOUR
                  ... Round to the start of the current hour
               NOW-1DAY
                  ... Exactly 1 day prior to now
               NOW/DAY+6MONTHS+3DAYS
                  ... 6 months and 3 days in the future from the start of
                      the current day

         Consult the DateField javadocs for more information.

         Note: For faster range queries, consider the tdate type
      -->
    <fieldType name="date" class="solr.TrieDateField" precisionStep="0"
positionIncrementGap="0"/>

    <!-- A Trie based date field for faster date range queries and date
faceting. -->
    <fieldType name="tdate" class="solr.TrieDateField" precisionStep="6"
positionIncrementGap="0"/>


    <!--Binary data type. The data should be sent/retrieved in as Base64
encoded Strings -->
    <fieldtype name="binary" class="solr.BinaryField"/>

    <!--
      Note:
      These should only be used for compatibility with existing indexes
(created with lucene or older Solr versions).
      Use Trie based fields instead. As of Solr 3.5 and 4.x, Trie based
fields support sortMissingFirst/Last

      Plain numeric field types that store and index the text
      value verbatim (and hence don't correctly support range queries,
since the
      lexicographic ordering isn't equal to the numeric ordering)

      NOTE: These field types are deprecated will be completely removed in
Solr 5.0!
    -->
    <!--
    <fieldType name="pint" class="solr.IntField"/>
    <fieldType name="plong" class="solr.LongField"/>
    <fieldType name="pfloat" class="solr.FloatField"/>
    <fieldType name="pdouble" class="solr.DoubleField"/>
    <fieldType name="pdate" class="solr.DateField" sortMissingLast="true"/>
    -->

    <!-- The "RandomSortField" is not used to store or search any
         data.  You can declare fields of this type it in your schema
         to generate pseudo-random orderings of your docs for sorting
         or function purposes.  The ordering is generated based on the field
         name and the version of the index. As long as the index version
         remains unchanged, and the same field name is reused,
         the ordering of the docs will be consistent.
         If you want different psuedo-random orderings of documents,
         for the same version of the index, use a dynamicField and
         change the field name in the request.
     -->
    <fieldType name="random" class="solr.RandomSortField" indexed="true" />

    <!-- solr.TextField allows the specification of custom text analyzers
         specified as a tokenizer and a list of token filters. Different
         analyzers may be specified for indexing and querying.

         The optional positionIncrementGap puts space between multiple
fields of
         this type on the same document, with the purpose of preventing
false phrase
         matching across fields.

         For more info on customizing your analyzer chain, please see
         http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters
     -->

    <!-- One can also specify an existing Analyzer class that has a
         default constructor via the class attribute on the analyzer
element.
         Example:
    <fieldType name="text_greek" class="solr.TextField">
      <analyzer class="org.apache.lucene.analysis.el.GreekAnalyzer"/>
    </fieldType>
    -->

    <!-- A text field that only splits on whitespace for exact matching of
words -->
    <fieldType name="text_ws" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
      </analyzer>
    </fieldType>

    <!-- A text type for English text where stopwords and synonyms are
managed using the REST API -->
    <fieldType name="managed_en" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.ManagedStopFilterFactory" managed="english" />
        <filter class="solr.ManagedSynonymFilterFactory" managed="english"
/>
      </analyzer>
    </fieldType>

    <!-- A general text field that has reasonable, generic
         cross-language defaults: it tokenizes with StandardTokenizer,
removes stop words from case-insensitive "stopwords.txt"
(empty by default), and down cases.  At query time only, it
also applies synonyms. -->
    <fieldType name="text_general" class="solr.TextField"
positionIncrementGap="100">
      <analyzer type="index">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <!-- in this example, we will only use synonyms at query time
        <filter class="solr.SynonymFilterFactory"
synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
        -->
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="true"/>
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- A general text field that has reasonable, generic
         cross-language defaults: it tokenizes with StandardTokenizer,
removes stop words from case-insensitive "stopwords.txt"
(empty by default), and down cases.  At query time only, it
also applies synonyms.
 IT HAS ALSO BEEN MODIFIED FROM DEFAULT TO STRIP HTML OUT -->
    <fieldType name="text_html" class="solr.TextField"
positionIncrementGap="100">
      <analyzer type="index">
<charFilter class="solr.HTMLStripCharFilterFactory"/>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <!-- in this example, we will only use synonyms at query time
        <filter class="solr.SynonymFilterFactory"
synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
        -->
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="true"/>
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- A text field with defaults appropriate for English: it
         tokenizes with StandardTokenizer, removes English stop words
         (lang/stopwords_en.txt), down cases, protects words from
protwords.txt, and
         finally applies Porter's stemming.  The query time analyzer
         also applies synonyms from synonyms.txt. -->
    <fieldType name="text_en" class="solr.TextField"
positionIncrementGap="100">
      <analyzer type="index">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- in this example, we will only use synonyms at query time
        <filter class="solr.SynonymFilterFactory"
synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
        -->
        <!-- Case insensitive stop word removal.
        -->
        <filter class="solr.StopFilterFactory"
                ignoreCase="true"
                words="lang/stopwords_en.txt"
                />
        <filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.EnglishPossessiveFilterFactory"/>
        <filter class="solr.KeywordMarkerFilterFactory"
protected="protwords.txt"/>
<!-- Optionally you may want to use this less aggressive stemmer instead of
PorterStemFilterFactory:
        <filter class="solr.EnglishMinimalStemFilterFactory"/>
-->
        <filter class="solr.PorterStemFilterFactory"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="true"/>
        <filter class="solr.StopFilterFactory"
                ignoreCase="true"
                words="lang/stopwords_en.txt"
                />
        <filter class="solr.LowerCaseFilterFactory"/>
<filter class="solr.EnglishPossessiveFilterFactory"/>
        <filter class="solr.KeywordMarkerFilterFactory"
protected="protwords.txt"/>
<!-- Optionally you may want to use this less aggressive stemmer instead of
PorterStemFilterFactory:
        <filter class="solr.EnglishMinimalStemFilterFactory"/>
-->
        <filter class="solr.PorterStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- A text field with defaults appropriate for English, plus
aggressive word-splitting and autophrase features enabled.
This field is just like text_en, except it adds
WordDelimiterFilter to enable splitting and matching of
words on case-change, alpha numeric boundaries, and
non-alphanumeric chars.  This means certain compound word
cases will work, for example query "wi fi" will match
document "WiFi" or "wi-fi".
        -->
    <fieldType name="text_en_splitting" class="solr.TextField"
positionIncrementGap="100" autoGeneratePhraseQueries="true">
      <analyzer type="index">
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
        <!-- in this example, we will only use synonyms at query time
        <filter class="solr.SynonymFilterFactory"
synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
        -->
        <!-- Case insensitive stop word removal.
        -->
        <filter class="solr.StopFilterFactory"
                ignoreCase="true"
                words="lang/stopwords_en.txt"
                />
        <filter class="solr.WordDelimiterFilterFactory"
generateWordParts="1" generateNumberParts="1" catenateWords="1"
catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.KeywordMarkerFilterFactory"
protected="protwords.txt"/>
        <filter class="solr.PorterStemFilterFactory"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="true"/>
        <filter class="solr.StopFilterFactory"
                ignoreCase="true"
                words="lang/stopwords_en.txt"
                />
        <filter class="solr.WordDelimiterFilterFactory"
generateWordParts="1" generateNumberParts="1" catenateWords="0"
catenateNumbers="0" catenateAll="0" splitOnCaseChange="1"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.KeywordMarkerFilterFactory"
protected="protwords.txt"/>
        <filter class="solr.PorterStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Less flexible matching, but less false matches.  Probably not
ideal for product names,
         but may be good for SKUs.  Can insert dashes in the wrong place
and still match. -->
    <fieldType name="text_en_splitting_tight" class="solr.TextField"
positionIncrementGap="100" autoGeneratePhraseQueries="true">
      <analyzer>
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="false"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_en.txt"/>
        <filter class="solr.WordDelimiterFilterFactory"
generateWordParts="0" generateNumberParts="0" catenateWords="1"
catenateNumbers="1" catenateAll="0"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.KeywordMarkerFilterFactory"
protected="protwords.txt"/>
        <filter class="solr.EnglishMinimalStemFilterFactory"/>
        <!-- this filter can remove any duplicate tokens that appear at the
same position - sometimes
             possible with WordDelimiterFilter in conjuncton with stemming.
-->
        <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Just like text_general except it reverses the characters of
each token, to enable more efficient leading wildcard queries. -->
    <fieldType name="text_general_rev" class="solr.TextField"
positionIncrementGap="100">
      <analyzer type="index">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.ReversedWildcardFilterFactory"
withOriginal="true"
           maxPosAsterisk="3" maxPosQuestion="2"
maxFractionAsterisk="0.33"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt"
ignoreCase="true" expand="true"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- charFilter + WhitespaceTokenizer  -->
    <!--
    <fieldType name="text_char_norm" class="solr.TextField"
positionIncrementGap="100" >
      <analyzer>
        <charFilter class="solr.MappingCharFilterFactory"
mapping="mapping-ISOLatin1Accent.txt"/>
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
      </analyzer>
    </fieldType>
    -->

    <!-- This is an example of using the KeywordTokenizer along
         With various TokenFilterFactories to produce a sortable field
         that does not include some properties of the source text
      -->
    <fieldType name="alphaOnlySort" class="solr.TextField"
sortMissingLast="true" omitNorms="true">
      <analyzer>
        <!-- KeywordTokenizer does no actual tokenizing, so the entire
             input string is preserved as a single token
          -->
        <tokenizer class="solr.KeywordTokenizerFactory"/>
        <!-- The LowerCase TokenFilter does what you expect, which can be
             when you want your sorting to be case insensitive
          -->
        <filter class="solr.LowerCaseFilterFactory" />
        <!-- The TrimFilter removes any leading or trailing whitespace -->
        <filter class="solr.TrimFilterFactory" />
        <!-- The PatternReplaceFilter gives you the flexibility to use
             Java Regular expression to replace any sequence of characters
             matching a pattern with an arbitrary replacement string,
             which may include back references to portions of the original
             string matched by the pattern.

             See the Java Regular Expression documentation for more
             information on pattern and replacement string syntax.


http://docs.oracle.com/javase/7/docs/api/java/util/regex/package-summary.html
          -->
        <filter class="solr.PatternReplaceFilterFactory"
                pattern="([^a-z])" replacement="" replace="all"
        />
      </analyzer>
    </fieldType>

    <fieldtype name="phonetic" stored="false" indexed="true"
class="solr.TextField" >
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.DoubleMetaphoneFilterFactory" inject="false"/>
      </analyzer>
    </fieldtype>

    <fieldtype name="payloads" stored="false" indexed="true"
class="solr.TextField" >
      <analyzer>
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
        <!--
        The DelimitedPayloadTokenFilter can put payloads on tokens... for
example,
        a token of "foo|1.4"  would be indexed as "foo" with a payload of
1.4f
        Attributes of the DelimitedPayloadTokenFilterFactory :
         "delimiter" - a one character delimiter. Default is | (pipe)
"encoder" - how to encode the following value into a playload
   float -> org.apache.lucene.analysis.payloads.FloatEncoder,
   integer -> o.a.l.a.p.IntegerEncoder
   identity -> o.a.l.a.p.IdentityEncoder
            Fully Qualified class name implementing PayloadEncoder, Encoder
must have a no arg constructor.
         -->
        <filter class="solr.DelimitedPayloadTokenFilterFactory"
encoder="float"/>
      </analyzer>
    </fieldtype>

    <!-- lowercases the entire field value, keeping it as a single token.
 -->
    <fieldType name="lowercase" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.KeywordTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory" />
      </analyzer>
    </fieldType>

    <!--
      Example of using PathHierarchyTokenizerFactory at index time, so
      queries for paths match documents at that path, or in descendent paths
    -->
    <fieldType name="descendent_path" class="solr.TextField">
      <analyzer type="index">
<tokenizer class="solr.PathHierarchyTokenizerFactory" delimiter="/" />
      </analyzer>
      <analyzer type="query">
<tokenizer class="solr.KeywordTokenizerFactory" />
      </analyzer>
    </fieldType>
    <!--
      Example of using PathHierarchyTokenizerFactory at query time, so
      queries for paths match documents at that path, or in ancestor paths
    -->
    <fieldType name="ancestor_path" class="solr.TextField">
      <analyzer type="index">
<tokenizer class="solr.KeywordTokenizerFactory" />
      </analyzer>
      <analyzer type="query">
<tokenizer class="solr.PathHierarchyTokenizerFactory" delimiter="/" />
      </analyzer>
    </fieldType>

    <!-- since fields of this type are by default not stored or indexed,
         any data added to them will be ignored outright.  -->
    <fieldtype name="ignored" stored="false" indexed="false"
multiValued="true" class="solr.StrField" />

    <!-- This point type indexes the coordinates as separate fields
(subFields)
      If subFieldType is defined, it references a type, and a dynamic field
      definition is created matching *___<typename>.  Alternately, if
      subFieldSuffix is defined, that is used to create the subFields.
      Example: if subFieldType="double", then the coordinates would be
        indexed in fields myloc_0___double,myloc_1___double.
      Example: if subFieldSuffix="_d" then the coordinates would be indexed
        in fields myloc_0_d,myloc_1_d
      The subFields are an implementation detail of the fieldType, and end
      users normally should not need to know about them.
     -->
    <fieldType name="point" class="solr.PointType" dimension="2"
subFieldSuffix="_d"/>

    <!-- A specialized field for geospatial search. If indexed, this
fieldType must not be multivalued. -->
    <fieldType name="location" class="solr.LatLonType"
subFieldSuffix="_coordinate"/>

    <!-- An alternative geospatial field type new to Solr 4.  It supports
multiValued and polygon shapes.
      For more information about this and other Spatial fields new to Solr
4, see:
      http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4
    -->
    <fieldType name="location_rpt"
class="solr.SpatialRecursivePrefixTreeFieldType"
        geo="true" distErrPct="0.025" maxDistErr="0.000009" units="degrees"
/>

   <!-- Money/currency field type. See
http://wiki.apache.org/solr/MoneyFieldType
        Parameters:
          defaultCurrency: Specifies the default currency if none
specified. Defaults to "USD"
          precisionStep:   Specifies the precisionStep for the TrieLong
field used for the amount
          providerClass:   Lets you plug in other exchange provider backend:
                           solr.FileExchangeRateProvider is the default and
takes one parameter:
                             currencyConfig: name of an xml file holding
exchange rates
                           solr.OpenExchangeRatesOrgProvider uses rates
from openexchangerates.org:
                             ratesFileLocation: URL or path to rates JSON
file (default latest.json on the web)
                             refreshInterval: Number of minutes between
each rates fetch (default: 1440, min: 60)
   -->
    <fieldType name="currency" class="solr.CurrencyField" precisionStep="8"
defaultCurrency="USD" currencyConfig="currency.xml" />



   <!-- some examples for different languages (generally ordered by ISO
code) -->

    <!-- Arabic -->
    <fieldType name="text_ar" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- for any non-arabic -->
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ar.txt" />
        <!-- normalizes ﻯ to ﻱ, etc -->
        <filter class="solr.ArabicNormalizationFilterFactory"/>
        <filter class="solr.ArabicStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Bulgarian -->
    <fieldType name="text_bg" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_bg.txt" />
        <filter class="solr.BulgarianStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Catalan -->
    <fieldType name="text_ca" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- removes l', etc -->
        <filter class="solr.ElisionFilterFactory" ignoreCase="true"
articles="lang/contractions_ca.txt"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ca.txt" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Catalan"/>
      </analyzer>
    </fieldType>

    <!-- CJK bigram (see text_ja for a Japanese configuration using
morphological analysis) -->
    <fieldType name="text_cjk" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- normalize width before bigram, as e.g. half-width dakuten
combine  -->
        <filter class="solr.CJKWidthFilterFactory"/>
        <!-- for any non-CJK -->
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.CJKBigramFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Kurdish -->
    <fieldType name="text_ckb" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.SoraniNormalizationFilterFactory"/>
        <!-- for any latin text -->
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ckb.txt"/>
        <filter class="solr.SoraniStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Czech -->
    <fieldType name="text_cz" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_cz.txt" />
        <filter class="solr.CzechStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Danish -->
    <fieldType name="text_da" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_da.txt" format="snowball" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Danish"/>
      </analyzer>
    </fieldType>

    <!-- German -->
    <fieldType name="text_de" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_de.txt" format="snowball" />
        <filter class="solr.GermanNormalizationFilterFactory"/>
        <filter class="solr.GermanLightStemFilterFactory"/>
        <!-- less aggressive: <filter
class="solr.GermanMinimalStemFilterFactory"/> -->
        <!-- more aggressive: <filter
class="solr.SnowballPorterFilterFactory" language="German2"/> -->
      </analyzer>
    </fieldType>

    <!-- Greek -->
    <fieldType name="text_el" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- greek specific lowercase for sigma -->
        <filter class="solr.GreekLowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="false"
words="lang/stopwords_el.txt" />
        <filter class="solr.GreekStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Spanish -->
    <fieldType name="text_es" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_es.txt" format="snowball" />
        <filter class="solr.SpanishLightStemFilterFactory"/>
        <!-- more aggressive: <filter
class="solr.SnowballPorterFilterFactory" language="Spanish"/> -->
      </analyzer>
    </fieldType>

    <!-- Basque -->
    <fieldType name="text_eu" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_eu.txt" />
        <filter class="solr.SnowballPorterFilterFactory" language="Basque"/>
      </analyzer>
    </fieldType>

    <!-- Persian -->
    <fieldType name="text_fa" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <!-- for ZWNJ -->
        <charFilter class="solr.PersianCharFilterFactory"/>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.ArabicNormalizationFilterFactory"/>
        <filter class="solr.PersianNormalizationFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_fa.txt" />
      </analyzer>
    </fieldType>

    <!-- Finnish -->
    <fieldType name="text_fi" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_fi.txt" format="snowball" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Finnish"/>
        <!-- less aggressive: <filter
class="solr.FinnishLightStemFilterFactory"/> -->
      </analyzer>
    </fieldType>

    <!-- French -->
    <fieldType name="text_fr" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- removes l', etc -->
        <filter class="solr.ElisionFilterFactory" ignoreCase="true"
articles="lang/contractions_fr.txt"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_fr.txt" format="snowball" />
        <filter class="solr.FrenchLightStemFilterFactory"/>
        <!-- less aggressive: <filter
class="solr.FrenchMinimalStemFilterFactory"/> -->
        <!-- more aggressive: <filter
class="solr.SnowballPorterFilterFactory" language="French"/> -->
      </analyzer>
    </fieldType>

    <!-- Irish -->
    <fieldType name="text_ga" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- removes d', etc -->
        <filter class="solr.ElisionFilterFactory" ignoreCase="true"
articles="lang/contractions_ga.txt"/>
        <!-- removes n-, etc. position increments is intentionally false!
-->
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/hyphenations_ga.txt"/>
        <filter class="solr.IrishLowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ga.txt"/>
        <filter class="solr.SnowballPorterFilterFactory" language="Irish"/>
      </analyzer>
    </fieldType>

    <!-- Galician -->
    <fieldType name="text_gl" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_gl.txt" />
        <filter class="solr.GalicianStemFilterFactory"/>
        <!-- less aggressive: <filter
class="solr.GalicianMinimalStemFilterFactory"/> -->
      </analyzer>
    </fieldType>

    <!-- Hindi -->
    <fieldType name="text_hi" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <!-- normalizes unicode representation -->
        <filter class="solr.IndicNormalizationFilterFactory"/>
        <!-- normalizes variation in spelling -->
        <filter class="solr.HindiNormalizationFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_hi.txt" />
        <filter class="solr.HindiStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Hungarian -->
    <fieldType name="text_hu" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_hu.txt" format="snowball" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Hungarian"/>
        <!-- less aggressive: <filter
class="solr.HungarianLightStemFilterFactory"/> -->
      </analyzer>
    </fieldType>

    <!-- Armenian -->
    <fieldType name="text_hy" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_hy.txt" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Armenian"/>
      </analyzer>
    </fieldType>

    <!-- Indonesian -->
    <fieldType name="text_id" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_id.txt" />
        <!-- for a less aggressive approach (only inflectional suffixes),
set stemDerivational to false -->
        <filter class="solr.IndonesianStemFilterFactory"
stemDerivational="true"/>
      </analyzer>
    </fieldType>

    <!-- Italian -->
    <fieldType name="text_it" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <!-- removes l', etc -->
        <filter class="solr.ElisionFilterFactory" ignoreCase="true"
articles="lang/contractions_it.txt"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_it.txt" format="snowball" />
        <filter class="solr.ItalianLightStemFilterFactory"/>
        <!-- more aggressive: <filter
class="solr.SnowballPorterFilterFactory" language="Italian"/> -->
      </analyzer>
    </fieldType>

    <!-- Japanese using morphological analysis (see text_cjk for a
configuration using bigramming)

         NOTE: If you want to optimize search for precision, use default
operator AND in your query
         parser config with <solrQueryParser defaultOperator="AND"/>
further down in this file.  Use
         OR if you would like to optimize for recall (default).
    -->
    <fieldType name="text_ja" class="solr.TextField"
positionIncrementGap="100" autoGeneratePhraseQueries="false">
      <analyzer>
      <!-- Kuromoji Japanese morphological analyzer/tokenizer
(JapaneseTokenizer)

           Kuromoji has a search mode (default) that does segmentation
useful for search.  A heuristic
           is used to segment compounds into its parts and the compound
itself is kept as synonym.

           Valid values for attribute mode are:
              normal: regular segmentation
              search: segmentation useful for search with synonyms
compounds (default)
            extended: same as search mode, but unigrams unknown words
(experimental)

           For some applications it might be good to use search mode for
indexing and normal mode for
           queries to reduce recall and prevent parts of compounds from
being matched and highlighted.
           Use <analyzer type="index"> and <analyzer type="query"> for this
and mode normal in query.

           Kuromoji also has a convenient user dictionary feature that
allows overriding the statistical
           model with your own entries for segmentation, part-of-speech
tags and readings without a need
           to specify weights.  Notice that user dictionaries have not been
subject to extensive testing.

           User dictionary attributes are:
                     userDictionary: user dictionary filename
             userDictionaryEncoding: user dictionary encoding (default is
UTF-8)

           See lang/userdict_ja.txt for a sample user dictionary file.

           Punctuation characters are discarded by default.  Use
discardPunctuation="false" to keep them.

           See http://wiki.apache.org/solr/JapaneseLanguageSupport for more
on Japanese language support.
        -->
        <tokenizer class="solr.JapaneseTokenizerFactory" mode="search"/>
        <!--<tokenizer class="solr.JapaneseTokenizerFactory" mode="search"
userDictionary="lang/userdict_ja.txt"/>-->
        <!-- Reduces inflected verbs and adjectives to their
base/dictionary forms (辞書形) -->
        <filter class="solr.JapaneseBaseFormFilterFactory"/>
        <!-- Removes tokens with certain part-of-speech tags -->
        <filter class="solr.JapanesePartOfSpeechStopFilterFactory"
tags="lang/stoptags_ja.txt" />
        <!-- Normalizes full-width romaji to half-width and half-width kana
to full-width (Unicode NFKC subset) -->
        <filter class="solr.CJKWidthFilterFactory"/>
        <!-- Removes common tokens typically not useful for search, but
have a negative effect on ranking -->
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ja.txt" />
        <!-- Normalizes common katakana spelling variations by removing any
last long sound character (U+30FC) -->
        <filter class="solr.JapaneseKatakanaStemFilterFactory"
minimumLength="4"/>
        <!-- Lower-cases romaji characters -->
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Latvian -->
    <fieldType name="text_lv" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_lv.txt" />
        <filter class="solr.LatvianStemFilterFactory"/>
      </analyzer>
    </fieldType>

    <!-- Dutch -->
    <fieldType name="text_nl" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_nl.txt" format="snowball" />
        <filter class="solr.StemmerOverrideFilterFactory"
dictionary="lang/stemdict_nl.txt" ignoreCase="false"/>
        <filter class="solr.SnowballPorterFilterFactory" language="Dutch"/>
      </analyzer>
    </fieldType>

    <!-- Norwegian -->
    <fieldType name="text_no" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_no.txt" format="snowball" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Norwegian"/>
        <!-- less aggressive: <filter
class="solr.NorwegianLightStemFilterFactory" variant="nb"/> -->
        <!-- singular/plural: <filter
class="solr.NorwegianMinimalStemFilterFactory" variant="nb"/> -->
        <!-- The "light" and "minimal" stemmers support variants:
nb=Bokmål, nn=Nynorsk, no=Both -->
      </analyzer>
    </fieldType>

    <!-- Portuguese -->
    <fieldType name="text_pt" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_pt.txt" format="snowball" />
        <filter class="solr.PortugueseLightStemFilterFactory"/>
        <!-- less aggressive: <filter
class="solr.PortugueseMinimalStemFilterFactory"/> -->
        <!-- more aggressive: <filter
class="solr.SnowballPorterFilterFactory" language="Portuguese"/> -->
        <!-- most aggressive: <filter
class="solr.PortugueseStemFilterFactory"/> -->
      </analyzer>
    </fieldType>

    <!-- Romanian -->
    <fieldType name="text_ro" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ro.txt" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Romanian"/>
      </analyzer>
    </fieldType>

    <!-- Russian -->
    <fieldType name="text_ru" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_ru.txt" format="snowball" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Russian"/>
        <!-- less aggressive: <filter
class="solr.RussianLightStemFilterFactory"/> -->
      </analyzer>
    </fieldType>

    <!-- Swedish -->
    <fieldType name="text_sv" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_sv.txt" format="snowball" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Swedish"/>
        <!-- less aggressive: <filter
class="solr.SwedishLightStemFilterFactory"/> -->
      </analyzer>
    </fieldType>

    <!-- Thai -->
    <fieldType name="text_th" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.ThaiTokenizerFactory"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="lang/stopwords_th.txt" />
      </analyzer>
    </fieldType>

    <!-- Turkish -->
    <fieldType name="text_tr" class="solr.TextField"
positionIncrementGap="100">
      <analyzer>
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.ApostropheFilterFactory"/>
        <filter class="solr.TurkishLowerCaseFilterFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="false"
words="lang/stopwords_tr.txt" />
        <filter class="solr.SnowballPorterFilterFactory"
language="Turkish"/>
      </analyzer>
    </fieldType>

  <!-- Similarity is the scoring routine for each document vs. a query.
       A custom Similarity or SimilarityFactory may be specified here, but
       the default is fine for most applications.
       For more info: http://wiki.apache.org/solr/SchemaXml#Similarity
    -->
  <!--
     <similarity class="com.example.solr.CustomSimilarityFactory">
       <str name="paramkey">param value</str>
     </similarity>
    -->

<xi:include href="statdx_custom_schema.xml" xmlns:xi="
http://www.w3.org/2001/XInclude"/>
</schema>

On Thu, Aug 4, 2016 at 5:26 PM, Chris Hostetter <ho...@fucit.org>
wrote:

>
> : The schema is a copy of the techproducts sample.
> :
> : Entire include here - and I take your point about the possibility of
> : malformation - thanks.
> :
> : I assumed (perhaps wrongly) that I could duplicate the <schema ...>
> :  </schema> arrangement from the schema.xml file.
>
> I really can't make heads or tails of what you're saying here -- what i
> asked you to provide was the full details on your schema.xml file and the
> file you are xincluding into it -- what you provided looks like a normal
> schema.xml, w/o any xinclude tags.  I also don't see any mention of any
> other files you are attempting to include in your schema.xml so i can see
> what it's structure looks like.
>
> For comparison, here is an example of a schema.xml file that uses an
> xinclude elements...
> https://github.com/apache/lucene-solr/blob/master/solr/
> core/src/test-files/solr/collection1/conf/schema-xinclude.xml
>
> Here is a specific example of one xinclude element from that file...
> <xi:include href="schema-snippet-type.xml"/>
>
> here is the file that is included by that xinclude element...
> https://github.com/apache/lucene-solr/blob/master/solr/
> core/src/test-files/solr/collection1/conf/schema-snippet-type.xml
>
>
> ...if you can provide the corrisponding specifics for your schema --
> showing the xinclude elements, and the files refrenced by them -- we can
> try to help make sense of why it's not working for you.
>
>
>
> :
> : I'm unfamiliar with xml entity includes, but I'll go look them up...
> :
> : <?xml version="1.0" encoding="UTF-8" ?>
> : <schema name="example" version="1.6">
> :
> :    <!-- ngram field to support suggestions / lookahead search on title
> (and
> : category, contentType)-->
> :    <copyField source="foobar" dest="text"/>
> :    <field name="suggestion_ngram_for_title" type="text_suggest_ngram"
> : indexed="true" stored="false"/>
> :    <field name="displayurl" type="text_general" indexed="true"
> : stored="true" multiValued="false"/>
> :    <field name="productVersionId" type="string" indexed="true"
> : stored="true" multiValued="false"/>
> :    <field name="caption" type="text_general" indexed="true" stored="true"
> : multiValued="false"/>
> :    <field name="documentId" type="string" indexed="true" stored="true"
> : multiValued="false"/>
> :    <!--<field name="category" type="string" indexed="true" stored="true"
> : multiValued="true"/>-->
> :    <field name="contentType" type="text_special_synonym" indexed="true"
> : stored="true" multiValued="false"/>
> :    <!-- Do NOT assume that much thought went into using int on the
> : following field. This is testing only!-->
> :    <field name="preference_" type="int" indexed="true" stored="true"
> : multiValued="false"/>
> :
> :    <field name="meta_doc_type" type="text_general" indexed="true"
> : stored="true" multiValued="false"/>
> :    <!--<field name="content" type="text_general" indexed="true"
> : stored="true" multiValued="false"/>-->
> :
> :    <!-- STATdx Weighting fields here. These are not part of the document,
> : but are used to calculate relevancy scores -->
> :    <field name="category_weight"  type="double" indexed="true"
> :  stored="true"/>    <!-- used for rule one - weighting docs on general
> : usefulness -->
> :
> :    <!-- Main body of document extracted by SolrCell.
> :         NOTE: This field is not indexed by default, since it is also
> copied
> : to "text"
> :         using copyField below. This is to save space. Use this field for
> : returning and
> :         highlighting document content. Use the "text" field to search the
> : content. -->
> :    <field name="content" type="text_en" indexed="false" stored="true"
> : multiValued="true"/> *//HERE IS WHERE "CONTENT" IS DEFINED*
> :
> : <!-- test for parsing statdx-provided html in content field. text_html
> has
> : been modified to clean html -->
> :    <field name="html_content" type="text_html" indexed="true"
> stored="true"
> : multiValued="true"/>
> :
> :    <!-- Text fields from SolrCell to search by default in our catch-all
> : field -->
> :    <copyField source="title" dest="text"/>
> :    <copyField source="author" dest="text"/>
> :    <copyField source="description" dest="text"/>
> :    <copyField source="keywords" dest="text"/>
> :    <copyField source="content" dest="text"/>  /*/THROWING ERROR ABOUT
> : "CONTENT" NOT EXISTING HERE*
> :    <copyField source="content_type" dest="text"/>
> :    <copyField source="resourcename" dest="text"/>
> :    <copyField source="url" dest="text"/>
> :
> :    <!-- Create a string version of author for faceting -->
> :    <copyField source="author" dest="author_s"/>
> :
> :   <!-- Above, multiple source fields are copied to the [text] field.
> :           Another way to map multiple source fields to the same
> :           destination field is to use the dynamic field syntax.
> :           copyField also supports a maxChars to copy setting.  -->
> :
> :         <copyField source="*_en" dest="text"/>
> :
> :
> :     <!-- a copy of text_general. Used to handle the rule that says that
> : docs with "table"
> :          and "tsm" in the contentType field should show at the top of
> : results IF any of the
> :          following terms are in the search term submitted by the user:
> :          [TNM, AJCC, Stage, Staging, FIGO]   Note the special synonym
> file
> : in the xml below.
> :          Note to self: Expand this documentation if we end up adding more
> : "special" synonyms -->
> :     <fieldType name="text_special_synonym" class="solr.TextField"
> : positionIncrementGap="100">
> :       <analyzer type="index">
> :         <tokenizer class="solr.StandardTokenizerFactory"/>
> :         <filter class="solr.StopFilterFactory" ignoreCase="true"
> : words="stopwords.txt" />
> :                 <!-- in this example, we will only use synonyms at query
> : time
> :         <filter class="solr.SynonymFilterFactory"
> : synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
> :         -->
> :         <filter class="solr.LowerCaseFilterFactory"/>
> :       </analyzer>
> :       <analyzer type="query">
> :         <tokenizer class="solr.StandardTokenizerFactory"/>
> :         <filter class="solr.StopFilterFactory" ignoreCase="true"
> : words="stopwords.txt" />
> :         <!-- Special synonym file here!!!!  -->
> :         <filter class="solr.SynonymFilterFactory"
> : synonyms="contentType_synonyms.txt" ignoreCase="true" expand="true"/>
> :         <filter class="solr.LowerCaseFilterFactory"/>
> :       </analyzer>
> :     </fieldType>
> :
> : </schema>
> :
> :
> :
> : On Thu, Aug 4, 2016 at 3:55 PM, Chris Hostetter <
> hossman_lucene@fucit.org>
> : wrote:
> :
> : >
> : > you mentioned that the problem only happens when you use xinclude, but
> you
> : > havne't shown us hte details of your xinclude -- what exactly does your
> : > schema.xml look like (with the xinclude call) and what exactly does the
> : > file being included look like (entire contents)
> : >
> : > (I suspect the problem you are seeing is realted to the way xinclude
> : > doens't really support "snippets" of malformed xml, and instead
> requires
> : > some root tag -- i can't imagine what root tag you are using in the
> : > included file that would play nicely with mixing/matching field
> : > declarations. ... using xml entity includes may be a simpler/safer
> option)
> : >
> : >
> : >
> : > : Date: Thu, 4 Aug 2016 15:47:00 -0600
> : > : From: John Bickerstaff <jo...@johnbickerstaff.com>
> : > : Reply-To: solr-user@lucene.apache.org
> : > : To: solr-user@lucene.apache.org
> : > : Subject: Re: Problems using fieldType text_general in copyField
> : > :
> : > : I would call this a bug...
> : > :
> : > : I'm going out on a limb and say that if you define a field in the
> : > included
> : > : XML file, you will get this error.
> : > :
> : > : As long as the field is defined first in schema.xml, you can
> "copyFIeld"
> : > it
> : > : or whatever in the include file, but apparently fields MUST be
> created in
> : > : the schema.xml file.
> : > :
> : > : That makes use of the include for custom things somewhat moot - at
> least
> : > in
> : > : my situation.
> : > :
> : > : I'd love to be wrong by the way, but that's what my tests suggest
> right
> : > : now...
> : > :
> : > : On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <
> : > john@johnbickerstaff.com>
> : > : wrote:
> : > :
> : > : > Summary:
> : > : >
> : > : > Using xinclude to include an xml file into schema.xml
> : > : >
> : > : > The following line
> : > : >
> : > : > <copyField source="content" dest="text"/>
> : > : >
> : > : > generates an error:  about a field being "not a glob and not
> matching
> : > an
> : > : > explicit field" even though I declare the field in the line just
> above.
> : > : >
> : > : > This seems to happen only for for fieldType text_general?
> : > : >
> : > : > ============
> : > : >
> : > : > Explanation:
> : > : >
> : > : > I need a little help - keep getting an error when trying to use the
> : > : > ability to include an additional XML file.  I may be overlooking
> : > something,
> : > : > but if so, I need help to see it.
> : > : >
> : > : > I have the following two lines which throw zero errors when part of
> : > : > schema.xml:
> : > : >
> : > : > <field name="content" type="text_general" indexed="false"
> stored="true"
> : > : > multiValued="true"/>
> : > : >  <copyField source="content" dest="text"/>
> : > : >
> : > : > However, when I put this into an include file and use xinclude,
> then I
> : > get
> : > : > this error when starting Solr.
> : > : >
> : > : >
> : > : >
> : > : >    - *statdx_shard1_replica3:* org.apache.solr.common.
> : > : >    SolrException:org.apache.solr.common.SolrException: Could not
> load
> : > : >    conf for core statdx_shard1_replica3: Can't load schema
> schema.xml:
> : > : >    copyField source :'content' is not a glob and doesn't match any
> : > explicit
> : > : >    field or dynamicField.
> : > : >
> : > : >
> : > : > Given that I am defining the field in the line right above the
> : > copyField
> : > : > statement, I'm confused about why this works fine in schema.xml but
> : > NOT in
> : > : > an included file.
> : > : >
> : > : > I experimented and found that any field of type "text_general" will
> : > throw
> : > : > this same error if it is part of the included xml file.  Other
> : > fieldTypes
> : > : > that I tried (string, int, double) did not have this issue.
> : > : >
> : > : > I'm using Solr 5.4, although I'm pulling custom config into an
> included
> : > : > file for purposes of moving to 6.1
> : > : >
> : > : > I have the following list of copyField commands in the included xml
> : > file,
> : > : > and get no errors on any but the "content" one.  It just so happens
> : > that
> : > : > "content" is the only field of type "text_general" in there.
> : > : >
> : > : >
> : > : > Any hints greatly appreciated.
> : > : >
> : > : >   <copyField source="title" dest="text"/>
> : > : >    <copyField source="author" dest="text"/>
> : > : >    <copyField source="description" dest="text"/>
> : > : >    <copyField source="keywords" dest="text"/>
> : > : >    <copyField source="content" dest="text"/>
> : > : >    <copyField source="content_type" dest="text"/>
> : > : >    <copyField source="resourcename" dest="text"/>
> : > : >    <copyField source="url" dest="text"/>
> : > : >
> : > : >
> : > :
> : >
> : > -Hoss
> : > http://www.lucidworks.com/
> : >
> :
>
> -Hoss
> http://www.lucidworks.com/
>

Re: Problems using fieldType text_general in copyField

Posted by Chris Hostetter <ho...@fucit.org>.
: The schema is a copy of the techproducts sample.
: 
: Entire include here - and I take your point about the possibility of
: malformation - thanks.
: 
: I assumed (perhaps wrongly) that I could duplicate the <schema ...>
:  </schema> arrangement from the schema.xml file.

I really can't make heads or tails of what you're saying here -- what i 
asked you to provide was the full details on your schema.xml file and the 
file you are xincluding into it -- what you provided looks like a normal 
schema.xml, w/o any xinclude tags.  I also don't see any mention of any 
other files you are attempting to include in your schema.xml so i can see 
what it's structure looks like.

For comparison, here is an example of a schema.xml file that uses an 
xinclude elements...
https://github.com/apache/lucene-solr/blob/master/solr/core/src/test-files/solr/collection1/conf/schema-xinclude.xml

Here is a specific example of one xinclude element from that file...
<xi:include href="schema-snippet-type.xml"/>

here is the file that is included by that xinclude element...
https://github.com/apache/lucene-solr/blob/master/solr/core/src/test-files/solr/collection1/conf/schema-snippet-type.xml


...if you can provide the corrisponding specifics for your schema -- 
showing the xinclude elements, and the files refrenced by them -- we can 
try to help make sense of why it's not working for you.



: 
: I'm unfamiliar with xml entity includes, but I'll go look them up...
: 
: <?xml version="1.0" encoding="UTF-8" ?>
: <schema name="example" version="1.6">
: 
:    <!-- ngram field to support suggestions / lookahead search on title (and
: category, contentType)-->
:    <copyField source="foobar" dest="text"/>
:    <field name="suggestion_ngram_for_title" type="text_suggest_ngram"
: indexed="true" stored="false"/>
:    <field name="displayurl" type="text_general" indexed="true"
: stored="true" multiValued="false"/>
:    <field name="productVersionId" type="string" indexed="true"
: stored="true" multiValued="false"/>
:    <field name="caption" type="text_general" indexed="true" stored="true"
: multiValued="false"/>
:    <field name="documentId" type="string" indexed="true" stored="true"
: multiValued="false"/>
:    <!--<field name="category" type="string" indexed="true" stored="true"
: multiValued="true"/>-->
:    <field name="contentType" type="text_special_synonym" indexed="true"
: stored="true" multiValued="false"/>
:    <!-- Do NOT assume that much thought went into using int on the
: following field. This is testing only!-->
:    <field name="preference_" type="int" indexed="true" stored="true"
: multiValued="false"/>
: 
:    <field name="meta_doc_type" type="text_general" indexed="true"
: stored="true" multiValued="false"/>
:    <!--<field name="content" type="text_general" indexed="true"
: stored="true" multiValued="false"/>-->
: 
:    <!-- STATdx Weighting fields here. These are not part of the document,
: but are used to calculate relevancy scores -->
:    <field name="category_weight"  type="double" indexed="true"
:  stored="true"/>    <!-- used for rule one - weighting docs on general
: usefulness -->
: 
:    <!-- Main body of document extracted by SolrCell.
:         NOTE: This field is not indexed by default, since it is also copied
: to "text"
:         using copyField below. This is to save space. Use this field for
: returning and
:         highlighting document content. Use the "text" field to search the
: content. -->
:    <field name="content" type="text_en" indexed="false" stored="true"
: multiValued="true"/> *//HERE IS WHERE "CONTENT" IS DEFINED*
: 
: <!-- test for parsing statdx-provided html in content field. text_html has
: been modified to clean html -->
:    <field name="html_content" type="text_html" indexed="true" stored="true"
: multiValued="true"/>
: 
:    <!-- Text fields from SolrCell to search by default in our catch-all
: field -->
:    <copyField source="title" dest="text"/>
:    <copyField source="author" dest="text"/>
:    <copyField source="description" dest="text"/>
:    <copyField source="keywords" dest="text"/>
:    <copyField source="content" dest="text"/>  /*/THROWING ERROR ABOUT
: "CONTENT" NOT EXISTING HERE*
:    <copyField source="content_type" dest="text"/>
:    <copyField source="resourcename" dest="text"/>
:    <copyField source="url" dest="text"/>
: 
:    <!-- Create a string version of author for faceting -->
:    <copyField source="author" dest="author_s"/>
: 
:   <!-- Above, multiple source fields are copied to the [text] field.
:           Another way to map multiple source fields to the same
:           destination field is to use the dynamic field syntax.
:           copyField also supports a maxChars to copy setting.  -->
: 
:         <copyField source="*_en" dest="text"/>
: 
: 
:     <!-- a copy of text_general. Used to handle the rule that says that
: docs with "table"
:          and "tsm" in the contentType field should show at the top of
: results IF any of the
:          following terms are in the search term submitted by the user:
:          [TNM, AJCC, Stage, Staging, FIGO]   Note the special synonym file
: in the xml below.
:          Note to self: Expand this documentation if we end up adding more
: "special" synonyms -->
:     <fieldType name="text_special_synonym" class="solr.TextField"
: positionIncrementGap="100">
:       <analyzer type="index">
:         <tokenizer class="solr.StandardTokenizerFactory"/>
:         <filter class="solr.StopFilterFactory" ignoreCase="true"
: words="stopwords.txt" />
:                 <!-- in this example, we will only use synonyms at query
: time
:         <filter class="solr.SynonymFilterFactory"
: synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
:         -->
:         <filter class="solr.LowerCaseFilterFactory"/>
:       </analyzer>
:       <analyzer type="query">
:         <tokenizer class="solr.StandardTokenizerFactory"/>
:         <filter class="solr.StopFilterFactory" ignoreCase="true"
: words="stopwords.txt" />
:         <!-- Special synonym file here!!!!  -->
:         <filter class="solr.SynonymFilterFactory"
: synonyms="contentType_synonyms.txt" ignoreCase="true" expand="true"/>
:         <filter class="solr.LowerCaseFilterFactory"/>
:       </analyzer>
:     </fieldType>
: 
: </schema>
: 
: 
: 
: On Thu, Aug 4, 2016 at 3:55 PM, Chris Hostetter <ho...@fucit.org>
: wrote:
: 
: >
: > you mentioned that the problem only happens when you use xinclude, but you
: > havne't shown us hte details of your xinclude -- what exactly does your
: > schema.xml look like (with the xinclude call) and what exactly does the
: > file being included look like (entire contents)
: >
: > (I suspect the problem you are seeing is realted to the way xinclude
: > doens't really support "snippets" of malformed xml, and instead requires
: > some root tag -- i can't imagine what root tag you are using in the
: > included file that would play nicely with mixing/matching field
: > declarations. ... using xml entity includes may be a simpler/safer option)
: >
: >
: >
: > : Date: Thu, 4 Aug 2016 15:47:00 -0600
: > : From: John Bickerstaff <jo...@johnbickerstaff.com>
: > : Reply-To: solr-user@lucene.apache.org
: > : To: solr-user@lucene.apache.org
: > : Subject: Re: Problems using fieldType text_general in copyField
: > :
: > : I would call this a bug...
: > :
: > : I'm going out on a limb and say that if you define a field in the
: > included
: > : XML file, you will get this error.
: > :
: > : As long as the field is defined first in schema.xml, you can "copyFIeld"
: > it
: > : or whatever in the include file, but apparently fields MUST be created in
: > : the schema.xml file.
: > :
: > : That makes use of the include for custom things somewhat moot - at least
: > in
: > : my situation.
: > :
: > : I'd love to be wrong by the way, but that's what my tests suggest right
: > : now...
: > :
: > : On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <
: > john@johnbickerstaff.com>
: > : wrote:
: > :
: > : > Summary:
: > : >
: > : > Using xinclude to include an xml file into schema.xml
: > : >
: > : > The following line
: > : >
: > : > <copyField source="content" dest="text"/>
: > : >
: > : > generates an error:  about a field being "not a glob and not matching
: > an
: > : > explicit field" even though I declare the field in the line just above.
: > : >
: > : > This seems to happen only for for fieldType text_general?
: > : >
: > : > ============
: > : >
: > : > Explanation:
: > : >
: > : > I need a little help - keep getting an error when trying to use the
: > : > ability to include an additional XML file.  I may be overlooking
: > something,
: > : > but if so, I need help to see it.
: > : >
: > : > I have the following two lines which throw zero errors when part of
: > : > schema.xml:
: > : >
: > : > <field name="content" type="text_general" indexed="false" stored="true"
: > : > multiValued="true"/>
: > : >  <copyField source="content" dest="text"/>
: > : >
: > : > However, when I put this into an include file and use xinclude, then I
: > get
: > : > this error when starting Solr.
: > : >
: > : >
: > : >
: > : >    - *statdx_shard1_replica3:* org.apache.solr.common.
: > : >    SolrException:org.apache.solr.common.SolrException: Could not load
: > : >    conf for core statdx_shard1_replica3: Can't load schema schema.xml:
: > : >    copyField source :'content' is not a glob and doesn't match any
: > explicit
: > : >    field or dynamicField.
: > : >
: > : >
: > : > Given that I am defining the field in the line right above the
: > copyField
: > : > statement, I'm confused about why this works fine in schema.xml but
: > NOT in
: > : > an included file.
: > : >
: > : > I experimented and found that any field of type "text_general" will
: > throw
: > : > this same error if it is part of the included xml file.  Other
: > fieldTypes
: > : > that I tried (string, int, double) did not have this issue.
: > : >
: > : > I'm using Solr 5.4, although I'm pulling custom config into an included
: > : > file for purposes of moving to 6.1
: > : >
: > : > I have the following list of copyField commands in the included xml
: > file,
: > : > and get no errors on any but the "content" one.  It just so happens
: > that
: > : > "content" is the only field of type "text_general" in there.
: > : >
: > : >
: > : > Any hints greatly appreciated.
: > : >
: > : >   <copyField source="title" dest="text"/>
: > : >    <copyField source="author" dest="text"/>
: > : >    <copyField source="description" dest="text"/>
: > : >    <copyField source="keywords" dest="text"/>
: > : >    <copyField source="content" dest="text"/>
: > : >    <copyField source="content_type" dest="text"/>
: > : >    <copyField source="resourcename" dest="text"/>
: > : >    <copyField source="url" dest="text"/>
: > : >
: > : >
: > :
: >
: > -Hoss
: > http://www.lucidworks.com/
: >
: 

-Hoss
http://www.lucidworks.com/

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
Thanks!

The schema is a copy of the techproducts sample.

Entire include here - and I take your point about the possibility of
malformation - thanks.

I assumed (perhaps wrongly) that I could duplicate the <schema ...>
 </schema> arrangement from the schema.xml file.

I'm unfamiliar with xml entity includes, but I'll go look them up...

<?xml version="1.0" encoding="UTF-8" ?>
<schema name="example" version="1.6">

   <!-- ngram field to support suggestions / lookahead search on title (and
category, contentType)-->
   <copyField source="foobar" dest="text"/>
   <field name="suggestion_ngram_for_title" type="text_suggest_ngram"
indexed="true" stored="false"/>
   <field name="displayurl" type="text_general" indexed="true"
stored="true" multiValued="false"/>
   <field name="productVersionId" type="string" indexed="true"
stored="true" multiValued="false"/>
   <field name="caption" type="text_general" indexed="true" stored="true"
multiValued="false"/>
   <field name="documentId" type="string" indexed="true" stored="true"
multiValued="false"/>
   <!--<field name="category" type="string" indexed="true" stored="true"
multiValued="true"/>-->
   <field name="contentType" type="text_special_synonym" indexed="true"
stored="true" multiValued="false"/>
   <!-- Do NOT assume that much thought went into using int on the
following field. This is testing only!-->
   <field name="preference_" type="int" indexed="true" stored="true"
multiValued="false"/>

   <field name="meta_doc_type" type="text_general" indexed="true"
stored="true" multiValued="false"/>
   <!--<field name="content" type="text_general" indexed="true"
stored="true" multiValued="false"/>-->

   <!-- STATdx Weighting fields here. These are not part of the document,
but are used to calculate relevancy scores -->
   <field name="category_weight"  type="double" indexed="true"
 stored="true"/>    <!-- used for rule one - weighting docs on general
usefulness -->

   <!-- Main body of document extracted by SolrCell.
        NOTE: This field is not indexed by default, since it is also copied
to "text"
        using copyField below. This is to save space. Use this field for
returning and
        highlighting document content. Use the "text" field to search the
content. -->
   <field name="content" type="text_en" indexed="false" stored="true"
multiValued="true"/> *//HERE IS WHERE "CONTENT" IS DEFINED*

<!-- test for parsing statdx-provided html in content field. text_html has
been modified to clean html -->
   <field name="html_content" type="text_html" indexed="true" stored="true"
multiValued="true"/>

   <!-- Text fields from SolrCell to search by default in our catch-all
field -->
   <copyField source="title" dest="text"/>
   <copyField source="author" dest="text"/>
   <copyField source="description" dest="text"/>
   <copyField source="keywords" dest="text"/>
   <copyField source="content" dest="text"/>  /*/THROWING ERROR ABOUT
"CONTENT" NOT EXISTING HERE*
   <copyField source="content_type" dest="text"/>
   <copyField source="resourcename" dest="text"/>
   <copyField source="url" dest="text"/>

   <!-- Create a string version of author for faceting -->
   <copyField source="author" dest="author_s"/>

  <!-- Above, multiple source fields are copied to the [text] field.
          Another way to map multiple source fields to the same
          destination field is to use the dynamic field syntax.
          copyField also supports a maxChars to copy setting.  -->

        <copyField source="*_en" dest="text"/>


    <!-- a copy of text_general. Used to handle the rule that says that
docs with "table"
         and "tsm" in the contentType field should show at the top of
results IF any of the
         following terms are in the search term submitted by the user:
         [TNM, AJCC, Stage, Staging, FIGO]   Note the special synonym file
in the xml below.
         Note to self: Expand this documentation if we end up adding more
"special" synonyms -->
    <fieldType name="text_special_synonym" class="solr.TextField"
positionIncrementGap="100">
      <analyzer type="index">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
                <!-- in this example, we will only use synonyms at query
time
        <filter class="solr.SynonymFilterFactory"
synonyms="index_synonyms.txt" ignoreCase="true" expand="false"/>
        -->
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.StandardTokenizerFactory"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true"
words="stopwords.txt" />
        <!-- Special synonym file here!!!!  -->
        <filter class="solr.SynonymFilterFactory"
synonyms="contentType_synonyms.txt" ignoreCase="true" expand="true"/>
        <filter class="solr.LowerCaseFilterFactory"/>
      </analyzer>
    </fieldType>

</schema>



On Thu, Aug 4, 2016 at 3:55 PM, Chris Hostetter <ho...@fucit.org>
wrote:

>
> you mentioned that the problem only happens when you use xinclude, but you
> havne't shown us hte details of your xinclude -- what exactly does your
> schema.xml look like (with the xinclude call) and what exactly does the
> file being included look like (entire contents)
>
> (I suspect the problem you are seeing is realted to the way xinclude
> doens't really support "snippets" of malformed xml, and instead requires
> some root tag -- i can't imagine what root tag you are using in the
> included file that would play nicely with mixing/matching field
> declarations. ... using xml entity includes may be a simpler/safer option)
>
>
>
> : Date: Thu, 4 Aug 2016 15:47:00 -0600
> : From: John Bickerstaff <jo...@johnbickerstaff.com>
> : Reply-To: solr-user@lucene.apache.org
> : To: solr-user@lucene.apache.org
> : Subject: Re: Problems using fieldType text_general in copyField
> :
> : I would call this a bug...
> :
> : I'm going out on a limb and say that if you define a field in the
> included
> : XML file, you will get this error.
> :
> : As long as the field is defined first in schema.xml, you can "copyFIeld"
> it
> : or whatever in the include file, but apparently fields MUST be created in
> : the schema.xml file.
> :
> : That makes use of the include for custom things somewhat moot - at least
> in
> : my situation.
> :
> : I'd love to be wrong by the way, but that's what my tests suggest right
> : now...
> :
> : On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <
> john@johnbickerstaff.com>
> : wrote:
> :
> : > Summary:
> : >
> : > Using xinclude to include an xml file into schema.xml
> : >
> : > The following line
> : >
> : > <copyField source="content" dest="text"/>
> : >
> : > generates an error:  about a field being "not a glob and not matching
> an
> : > explicit field" even though I declare the field in the line just above.
> : >
> : > This seems to happen only for for fieldType text_general?
> : >
> : > ============
> : >
> : > Explanation:
> : >
> : > I need a little help - keep getting an error when trying to use the
> : > ability to include an additional XML file.  I may be overlooking
> something,
> : > but if so, I need help to see it.
> : >
> : > I have the following two lines which throw zero errors when part of
> : > schema.xml:
> : >
> : > <field name="content" type="text_general" indexed="false" stored="true"
> : > multiValued="true"/>
> : >  <copyField source="content" dest="text"/>
> : >
> : > However, when I put this into an include file and use xinclude, then I
> get
> : > this error when starting Solr.
> : >
> : >
> : >
> : >    - *statdx_shard1_replica3:* org.apache.solr.common.
> : >    SolrException:org.apache.solr.common.SolrException: Could not load
> : >    conf for core statdx_shard1_replica3: Can't load schema schema.xml:
> : >    copyField source :'content' is not a glob and doesn't match any
> explicit
> : >    field or dynamicField.
> : >
> : >
> : > Given that I am defining the field in the line right above the
> copyField
> : > statement, I'm confused about why this works fine in schema.xml but
> NOT in
> : > an included file.
> : >
> : > I experimented and found that any field of type "text_general" will
> throw
> : > this same error if it is part of the included xml file.  Other
> fieldTypes
> : > that I tried (string, int, double) did not have this issue.
> : >
> : > I'm using Solr 5.4, although I'm pulling custom config into an included
> : > file for purposes of moving to 6.1
> : >
> : > I have the following list of copyField commands in the included xml
> file,
> : > and get no errors on any but the "content" one.  It just so happens
> that
> : > "content" is the only field of type "text_general" in there.
> : >
> : >
> : > Any hints greatly appreciated.
> : >
> : >   <copyField source="title" dest="text"/>
> : >    <copyField source="author" dest="text"/>
> : >    <copyField source="description" dest="text"/>
> : >    <copyField source="keywords" dest="text"/>
> : >    <copyField source="content" dest="text"/>
> : >    <copyField source="content_type" dest="text"/>
> : >    <copyField source="resourcename" dest="text"/>
> : >    <copyField source="url" dest="text"/>
> : >
> : >
> :
>
> -Hoss
> http://www.lucidworks.com/
>

Re: Problems using fieldType text_general in copyField

Posted by Chris Hostetter <ho...@fucit.org>.
you mentioned that the problem only happens when you use xinclude, but you 
havne't shown us hte details of your xinclude -- what exactly does your 
schema.xml look like (with the xinclude call) and what exactly does the 
file being included look like (entire contents)

(I suspect the problem you are seeing is realted to the way xinclude 
doens't really support "snippets" of malformed xml, and instead requires 
some root tag -- i can't imagine what root tag you are using in the 
included file that would play nicely with mixing/matching field 
declarations. ... using xml entity includes may be a simpler/safer option)



: Date: Thu, 4 Aug 2016 15:47:00 -0600
: From: John Bickerstaff <jo...@johnbickerstaff.com>
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: Problems using fieldType text_general in copyField
: 
: I would call this a bug...
: 
: I'm going out on a limb and say that if you define a field in the included
: XML file, you will get this error.
: 
: As long as the field is defined first in schema.xml, you can "copyFIeld" it
: or whatever in the include file, but apparently fields MUST be created in
: the schema.xml file.
: 
: That makes use of the include for custom things somewhat moot - at least in
: my situation.
: 
: I'd love to be wrong by the way, but that's what my tests suggest right
: now...
: 
: On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <jo...@johnbickerstaff.com>
: wrote:
: 
: > Summary:
: >
: > Using xinclude to include an xml file into schema.xml
: >
: > The following line
: >
: > <copyField source="content" dest="text"/>
: >
: > generates an error:  about a field being "not a glob and not matching an
: > explicit field" even though I declare the field in the line just above.
: >
: > This seems to happen only for for fieldType text_general?
: >
: > ============
: >
: > Explanation:
: >
: > I need a little help - keep getting an error when trying to use the
: > ability to include an additional XML file.  I may be overlooking something,
: > but if so, I need help to see it.
: >
: > I have the following two lines which throw zero errors when part of
: > schema.xml:
: >
: > <field name="content" type="text_general" indexed="false" stored="true"
: > multiValued="true"/>
: >  <copyField source="content" dest="text"/>
: >
: > However, when I put this into an include file and use xinclude, then I get
: > this error when starting Solr.
: >
: >
: >
: >    - *statdx_shard1_replica3:* org.apache.solr.common.
: >    SolrException:org.apache.solr.common.SolrException: Could not load
: >    conf for core statdx_shard1_replica3: Can't load schema schema.xml:
: >    copyField source :'content' is not a glob and doesn't match any explicit
: >    field or dynamicField.
: >
: >
: > Given that I am defining the field in the line right above the copyField
: > statement, I'm confused about why this works fine in schema.xml but NOT in
: > an included file.
: >
: > I experimented and found that any field of type "text_general" will throw
: > this same error if it is part of the included xml file.  Other fieldTypes
: > that I tried (string, int, double) did not have this issue.
: >
: > I'm using Solr 5.4, although I'm pulling custom config into an included
: > file for purposes of moving to 6.1
: >
: > I have the following list of copyField commands in the included xml file,
: > and get no errors on any but the "content" one.  It just so happens that
: > "content" is the only field of type "text_general" in there.
: >
: >
: > Any hints greatly appreciated.
: >
: >   <copyField source="title" dest="text"/>
: >    <copyField source="author" dest="text"/>
: >    <copyField source="description" dest="text"/>
: >    <copyField source="keywords" dest="text"/>
: >    <copyField source="content" dest="text"/>
: >    <copyField source="content_type" dest="text"/>
: >    <copyField source="resourcename" dest="text"/>
: >    <copyField source="url" dest="text"/>
: >
: >
: 

-Hoss
http://www.lucidworks.com/

Re: Problems using fieldType text_general in copyField

Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
I would call this a bug...

I'm going out on a limb and say that if you define a field in the included
XML file, you will get this error.

As long as the field is defined first in schema.xml, you can "copyFIeld" it
or whatever in the include file, but apparently fields MUST be created in
the schema.xml file.

That makes use of the include for custom things somewhat moot - at least in
my situation.

I'd love to be wrong by the way, but that's what my tests suggest right
now...

On Thu, Aug 4, 2016 at 1:37 PM, John Bickerstaff <jo...@johnbickerstaff.com>
wrote:

> Summary:
>
> Using xinclude to include an xml file into schema.xml
>
> The following line
>
> <copyField source="content" dest="text"/>
>
> generates an error:  about a field being "not a glob and not matching an
> explicit field" even though I declare the field in the line just above.
>
> This seems to happen only for for fieldType text_general?
>
> ============
>
> Explanation:
>
> I need a little help - keep getting an error when trying to use the
> ability to include an additional XML file.  I may be overlooking something,
> but if so, I need help to see it.
>
> I have the following two lines which throw zero errors when part of
> schema.xml:
>
> <field name="content" type="text_general" indexed="false" stored="true"
> multiValued="true"/>
>  <copyField source="content" dest="text"/>
>
> However, when I put this into an include file and use xinclude, then I get
> this error when starting Solr.
>
>
>
>    - *statdx_shard1_replica3:* org.apache.solr.common.
>    SolrException:org.apache.solr.common.SolrException: Could not load
>    conf for core statdx_shard1_replica3: Can't load schema schema.xml:
>    copyField source :'content' is not a glob and doesn't match any explicit
>    field or dynamicField.
>
>
> Given that I am defining the field in the line right above the copyField
> statement, I'm confused about why this works fine in schema.xml but NOT in
> an included file.
>
> I experimented and found that any field of type "text_general" will throw
> this same error if it is part of the included xml file.  Other fieldTypes
> that I tried (string, int, double) did not have this issue.
>
> I'm using Solr 5.4, although I'm pulling custom config into an included
> file for purposes of moving to 6.1
>
> I have the following list of copyField commands in the included xml file,
> and get no errors on any but the "content" one.  It just so happens that
> "content" is the only field of type "text_general" in there.
>
>
> Any hints greatly appreciated.
>
>   <copyField source="title" dest="text"/>
>    <copyField source="author" dest="text"/>
>    <copyField source="description" dest="text"/>
>    <copyField source="keywords" dest="text"/>
>    <copyField source="content" dest="text"/>
>    <copyField source="content_type" dest="text"/>
>    <copyField source="resourcename" dest="text"/>
>    <copyField source="url" dest="text"/>
>
>