Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of benedetti.alex85@gmail.com
 designates 209.85.218.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAP3oLuDUY4uoUpOuAp_KXMfkit9nmEz+1G0PJ1KBmzw8n+b2=Q@mail.gmail.com>
References: 
 <CAP3oLuAA45hOEEN0hQ5n9s6bnK4B72_Mew+=k9zRk3PfOuzbVA@mail.gmail.com>
	<CAB-fSbxk92mwH8Q5Kfb-9Qj0OPNSCusYXA5K+VovcAds6of-gg@mail.gmail.com>
	<CAP3oLuBmRvrknE29hjOC6HR_YCCqKmmAJP60teNaqxXUNcQq+w@mail.gmail.com>
	<CAN4YXvevfQzh2UsLk17==FO0CEQQR6yLG1Kyan=zP8C85WYh=A@mail.gmail.com>
	<CAP3oLuCnMYaHoEV9c9tvo92-FxP1V98vYXMjdzpsr+e2wcAGtQ@mail.gmail.com>
	<CAB-fSbyQynBZt5E1gwp06fqDongMqBDF-2983G5y7e_uU8yPZQ@mail.gmail.com>
	<CAP3oLuDUY4uoUpOuAp_KXMfkit9nmEz+1G0PJ1KBmzw8n+b2=Q@mail.gmail.com>
Date: Tue, 30 Jun 2015 17:11:23 +0100
Message-ID: 
 <CAB-fSbywkVRbEtKRhQG4ZuNAbJAQuHq2yN9pRpvRa=PpfWOjGg@mail.gmail.com>
Subject: Re: Upgrade to 5.2 from 4.6, no storing of text
From: Alessandro Benedetti <benedetti.alex85@gmail.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=047d7b3a9cb02d44880519be7534

--047d7b3a9cb02d44880519be7534
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

No worries, it is not a big deal you shared the schema.xml, I said that
only because it turned the mail a little hard to read, anyway, in my
opinion the query is correct, so the problem should reside elsewhere.

Can you share the solrconfig.xml piece for your select request handler ?
Probably it is not the problem, but can give us more info.
I find text to be stored, so highlighting should work.

>From official documentation :

"The standard highlighter (AKA the default highlighter) doesn't require any
special indexing parameters on the fields to highlight.  However you can
optionally turn on termVectors, termPositions, and termOffsets for any
field to be highlighted. This will avoid having to run documents through
the analysis chain at query-time and will make highlighting significantly
faster and use less memory, particularly for large text fields, and even
more so when hl.usePhraseHighlighter is enabled."

So you should be ok.

Keep us posted


2015-06-30 16:00 GMT+01:00 Mark Ehle <markehle@gmail.com>:

> Alessandro -
>
> Someone asked to see the schema, I posted it. Should I have just attached
> it? Does this mailing list support that?
>
> I am by no means a SOLR expert. I am a PHP coder who wrote a
> (very-much-loved by our library staff and patrons) newspaper indexing too=
l
> that I am trying to update. I only know enough about SOLR to install it,
> and index and query. All I did to the 5.2 schema was add the
> newspaper-specific fields that was in the old schema.
>
> I cannot answer most of your questions. I just know that this url:
>
> http://127.0.0.1:8080/solr/newspapers/select?q=3D%22JOHN+GRAP%22&fl=3Dyea=
r&wt=3Djson&indent=3Dtrue&hl=3Dtrue&hl.fl=3Dtext&hl.simple.pre=3D%3Cem%3E&h=
l.simple.post=3D%3C%2Fem%3E
>
> used to produce snippets of highlited text in 4.6. In 5.2 it does not.
>
>
> Thanks -
>
> Mark Ehle
> Computer Support Librarian
> Willard Library
> Battle Creek, MI
>
>
> On Tue, Jun 30, 2015 at 10:50 AM, Alessandro Benedetti <
> benedetti.alex85@gmail.com> wrote:
>
> > Instead of your immense schema, can you give us the details of the
> > Highlight you are trying to use ?
> > And how you are trying to use it ?
> > Which client ? Direct APi calls ?
> >
> > let us know!
> >
> > Cheers
> >
> > 2015-06-30 15:10 GMT+01:00 Mark Ehle <markehle@gmail.com>:
> >
> > > Thanks to all for the help - it's now storing text and I can search a=
nd
> > get
> > > results just before in 4.6, but I cannot get snippets to appear when =
I
> > ask
> > > for highlighting.
> > >
> > >
> > > when I add documents, here is the URL my script generates:
> > >
> > >
> > >
> >
> http://localhost:8080/solr/newspapers/update/extract?literal.id=3D2015_01=
_01_battlecreekenquirer-004&literal.publication_date=3D2015-01-01T00:00:00Z=
&literal.year=3D2015&literal.yearstr=3D2015&literal.day=3D1&literal.month_n=
um=3D1&literal.month=3D01_January&literal.publication_name=3DBattle%20Creek=
%20Enquirer&literal.publication_type=3Dnewspaper&literal.short_name=3Dbattl=
ecreekenquirer&literal.image_number=3D4&literal.filename=3D2015_01_01_battl=
ecreekenquirer-004.pdf&literal.copyright_year=3D1923&literal.copyright_rest=
ricted=3Dy&fmap.content=3Dpublication_text&stream.contentType=3Dapplication=
%2Ftxt&stream.file=3D%2Farchive_data%2Fnewspapers%2FBattle%20Creek%20Enquir=
er%2F2015%2F01_January%2F2015_01_01_battlecreekenquirer%2Ftxt%2F2015_01_01_=
battlecreekenquirer-004.txt
> > >
> > >
> > > And here is my schema:
> > >
> > > <?xml version=3D"1.0" encoding=3D"UTF-8" ?>
> > >
> > > <!--
> > >  Licensed to the Apache Software Foundation (ASF) under one or more
> > >  contributor license agreements.  See the NOTICE file distributed wit=
h
> > >  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=3D"false" for all fields possible (esp large fields) w=
hen
> > you
> > >     only need to search on the field but don't need to return the
> > original
> > >     value.
> > >   - set indexed=3D"false" if you don't need to search on the field, b=
ut
> > 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 fal=
se
> > >     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 StreamingUpdateSolrServ=
er
> > >     java client.
> > >   - Remember to run the JVM in server mode, and use a higher logging
> > level
> > >     that avoids logging every request
> > > -->
> > >
> > > <schema name=3D"example" version=3D"1.4">
> > >   <!-- attribute "name" is the name of this schema and is only used f=
or
> > > display purposes.
> > >        Applications should change this to reflect the nature of the
> > search
> > > collection.
> > >        version=3D"1.4" 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: default auto-phrase (QueryParser feature) to off
> > >      -->
> > >
> > >   <types>
> > >     <!-- 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 th=
e
> > >        org.apache.solr.analysis package.
> > >     -->
> > >
> > >     <!-- The StrField type is not analyzed, but indexed/stored
> verbatim.
> > > -->
> > >     <fieldType name=3D"string" class=3D"solr.StrField"
> sortMissingLast=3D"true"
> > > omitNorms=3D"true"/>
> > >
> > >     <!-- boolean type: "true" or "false" -->
> > >     <fieldType name=3D"boolean" class=3D"solr.BoolField"
> > sortMissingLast=3D"true"
> > > omitNorms=3D"true"/>
> > >     <!--Binary data type. The data should be sent/retrieved in as
> Base64
> > > encoded Strings -->
> > >     <fieldtype name=3D"binary" class=3D"solr.BinaryField"/>
> > >
> > >     <!-- The optional sortMissingLast and sortMissingFirst attributes
> are
> > >          currently supported on types that are sorted internally as
> > > strings.
> > >                This includes
> > > "string","boolean","sint","slong","sfloat","sdouble","pdate"
> > >        - If sortMissingLast=3D"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=3D"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=3D"false" and sortMissingFirst=3D"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.
> > >     -->
> > >     <fieldType name=3D"int" class=3D"solr.TrieIntField" precisionStep=
=3D"0"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >     <fieldType name=3D"float" class=3D"solr.TrieFloatField"
> precisionStep=3D"0"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >     <fieldType name=3D"long" class=3D"solr.TrieLongField" precisionSt=
ep=3D"0"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >     <fieldType name=3D"double" class=3D"solr.TrieDoubleField"
> > precisionStep=3D"0"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >
> > >     <!--
> > >      Numeric field types that index each value at various levels of
> > > precision
> > >      to accelerate range queries when the number of values between th=
e
> > > range
> > >      endpoints is large. See the javadoc for NumericRangeQuery for
> > internal
> > >      implementation details.
> > >
> > >      Smaller precisionStep values (specified in bits) will lead to mo=
re
> > > tokens
> > >      indexed per value, slightly larger index size, and faster range
> > > queries.
> > >      A precisionStep of 0 disables indexing at different precision
> > levels.
> > >     -->
> > >     <fieldType name=3D"tint" class=3D"solr.TrieIntField" precisionSte=
p=3D"8"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >     <fieldType name=3D"tfloat" class=3D"solr.TrieFloatField"
> > precisionStep=3D"8"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >     <fieldType name=3D"tlong" class=3D"solr.TrieLongField"
> precisionStep=3D"8"
> > > omitNorms=3D"true" positionIncrementGap=3D"0"/>
> > >     <fieldType name=3D"tdouble" class=3D"solr.TrieDoubleField"
> > > precisionStep=3D"8" omitNorms=3D"true" positionIncrementGap=3D"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 star=
t
> of
> > >                       the current day
> > >
> > >          Consult the DateField javadocs for more information.
> > >
> > >          Note: For faster range queries, consider the tdate type
> > >       -->
> > >     <fieldType name=3D"date" class=3D"solr.TrieDateField" omitNorms=
=3D"true"
> > > precisionStep=3D"0" positionIncrementGap=3D"0"/>
> > >
> > >     <!-- A Trie based date field for faster date range queries and da=
te
> > > faceting. -->
> > >     <fieldType name=3D"tdate" class=3D"solr.TrieDateField" omitNorms=
=3D"true"
> > > precisionStep=3D"6" positionIncrementGap=3D"0"/>
> > >
> > >
> > >     <!--
> > >       Note:
> > >       These should only be used for compatibility with existing index=
es
> > > (created with older Solr versions)
> > >       or if "sortMissingFirst" or "sortMissingLast" functionality is
> > > needed. Use Trie based fields instead.
> > >
> > >       Plain numeric field types that store and index the text
> > >       value verbatim (and hence don't support range queries, since th=
e
> > >       lexicographic ordering isn't equal to the numeric ordering)
> > >     -->
> > >
> > >
> > >     <!--
> > >       Note:
> > >       These should only be used for compatibility with existing index=
es
> > > (created with older Solr versions)
> > >       or if "sortMissingFirst" or "sortMissingLast" functionality is
> > > needed. Use Trie based fields instead.
> > >
> > >       Numeric field types that manipulate the value into
> > >       a string value that isn't human-readable in its internal form,
> > >       but with a lexicographic ordering the same as the numeric
> ordering,
> > >       so that range queries work correctly.
> > >     -->
> > >     <fieldType name=3D"sint" class=3D"solr.SortableIntField"
> > > sortMissingLast=3D"true" omitNorms=3D"true"/>
> > >     <fieldType name=3D"slong" class=3D"solr.SortableLongField"
> > > sortMissingLast=3D"true" omitNorms=3D"true"/>
> > >     <fieldType name=3D"sfloat" class=3D"solr.SortableFloatField"
> > > sortMissingLast=3D"true" omitNorms=3D"true"/>
> > >     <fieldType name=3D"sdouble" class=3D"solr.SortableDoubleField"
> > > sortMissingLast=3D"true" omitNorms=3D"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
> > >          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 name
> > >      -->
> > >     <fieldType name=3D"random" class=3D"solr.RandomSortField"
> indexed=3D"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 multipl=
e
> > > fields of
> > >          this type on the same document, with the purpose of preventi=
ng
> > > 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
> > >     <fieldType name=3D"text_greek" class=3D"solr.TextField">
> > >       <analyzer class=3D"org.apache.lucene.analysis.el.GreekAnalyzer"=
/>
> > >     </fieldType>
> > >     -->
> > >
> > >     <!-- A text field that only splits on whitespace for exact matchi=
ng
> > of
> > > words -->
> > >     <fieldType name=3D"text_ws" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100">
> > >       <analyzer>
> > >         <tokenizer class=3D"solr.WhitespaceTokenizerFactory"/>
> > >       </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=3D"text_general" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100">
> > >       <analyzer type=3D"index">
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <filter class=3D"solr.StopFilterFactory" ignoreCase=3D"true"
> > > words=3D"stopwords.txt" enablePositionIncrements=3D"true" />
> > >         <!-- in this example, we will only use synonyms at query time
> > >         <filter class=3D"solr.SynonymFilterFactory"
> > > synonyms=3D"index_synonyms.txt" ignoreCase=3D"true" expand=3D"false"/=
>
> > >         -->
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >       </analyzer>
> > >       <analyzer type=3D"query">
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <filter class=3D"solr.StopFilterFactory" ignoreCase=3D"true"
> > > words=3D"stopwords.txt" enablePositionIncrements=3D"true" />
> > >         <filter class=3D"solr.SynonymFilterFactory"
> synonyms=3D"synonyms.txt"
> > > ignoreCase=3D"true" expand=3D"true"/>
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >       </analyzer>
> > >     </fieldType>
> > >
> > >     <!-- A text field with defaults appropriate for English: it
> > >          tokenizes with StandardTokenizer, removes English stop words
> > >          (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=3D"text_en" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100">
> > >       <analyzer type=3D"index">
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <!-- in this example, we will only use synonyms at query time
> > >         <filter class=3D"solr.SynonymFilterFactory"
> > > synonyms=3D"index_synonyms.txt" ignoreCase=3D"true" expand=3D"false"/=
>
> > >         -->
> > >         <!-- Case insensitive stop word removal.
> > >           add enablePositionIncrements=3Dtrue in both the index and q=
uery
> > >           analyzers to leave a 'gap' for more accurate phrase queries=
.
> > >         -->
> > >         <filter class=3D"solr.StopFilterFactory"
> > >                 ignoreCase=3D"true"
> > >                 words=3D"stopwords_en.txt"
> > >                 enablePositionIncrements=3D"true"
> > >                 />
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >         <filter class=3D"solr.EnglishPossessiveFilterFactory"/>
> > >         <filter class=3D"solr.KeywordMarkerFilterFactory"
> > > protected=3D"protwords.txt"/>
> > >         <!-- Optionally you may want to use this less aggressive
> stemmer
> > > instead of PorterStemFilterFactory:
> > >         <filter class=3D"solr.EnglishMinimalStemFilterFactory"/>
> > >         -->
> > >         <filter class=3D"solr.PorterStemFilterFactory"/>
> > >       </analyzer>
> > >       <analyzer type=3D"query">
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <filter class=3D"solr.SynonymFilterFactory"
> synonyms=3D"synonyms.txt"
> > > ignoreCase=3D"true" expand=3D"true"/>
> > >         <filter class=3D"solr.StopFilterFactory"
> > >                 ignoreCase=3D"true"
> > >                 words=3D"stopwords_en.txt"
> > >                 enablePositionIncrements=3D"true"
> > >                 />
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >         <filter class=3D"solr.EnglishPossessiveFilterFactory"/>
> > >         <filter class=3D"solr.KeywordMarkerFilterFactory"
> > > protected=3D"protwords.txt"/>
> > >         <!-- Optionally you may want to use this less aggressive
> stemmer
> > > instead of PorterStemFilterFactory:
> > >         <filter class=3D"solr.EnglishMinimalStemFilterFactory"/>
> > >         -->
> > >         <filter class=3D"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".  However, other cases will still
> > >          not match, for example if the query is "wifi" and the
> > >          document is "wi fi" or if the query is "wi-fi" and the
> > >          document is "wifi".
> > >         -->
> > >     <fieldType name=3D"text_en_splitting" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100" autoGeneratePhraseQueries=3D"true">
> > >       <analyzer type=3D"index">
> > >         <tokenizer class=3D"solr.WhitespaceTokenizerFactory"/>
> > >         <!-- in this example, we will only use synonyms at query time
> > >         <filter class=3D"solr.SynonymFilterFactory"
> > > synonyms=3D"index_synonyms.txt" ignoreCase=3D"true" expand=3D"false"/=
>
> > >         -->
> > >         <!-- Case insensitive stop word removal.
> > >           add enablePositionIncrements=3Dtrue in both the index and q=
uery
> > >           analyzers to leave a 'gap' for more accurate phrase queries=
.
> > >         -->
> > >         <filter class=3D"solr.StopFilterFactory"
> > >                 ignoreCase=3D"true"
> > >                 words=3D"stopwords_en.txt"
> > >                 enablePositionIncrements=3D"true"
> > >                 />
> > >         <filter class=3D"solr.WordDelimiterFilterFactory"
> > > generateWordParts=3D"1" generateNumberParts=3D"1" catenateWords=3D"1"
> > > catenateNumbers=3D"1" catenateAll=3D"0" splitOnCaseChange=3D"1"/>
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >         <filter class=3D"solr.KeywordMarkerFilterFactory"
> > > protected=3D"protwords.txt"/>
> > >         <filter class=3D"solr.PorterStemFilterFactory"/>
> > >       </analyzer>
> > >       <analyzer type=3D"query">
> > >         <tokenizer class=3D"solr.WhitespaceTokenizerFactory"/>
> > >         <filter class=3D"solr.SynonymFilterFactory"
> synonyms=3D"synonyms.txt"
> > > ignoreCase=3D"true" expand=3D"true"/>
> > >         <filter class=3D"solr.StopFilterFactory"
> > >                 ignoreCase=3D"true"
> > >                 words=3D"stopwords_en.txt"
> > >                 enablePositionIncrements=3D"true"
> > >                 />
> > >         <filter class=3D"solr.WordDelimiterFilterFactory"
> > > generateWordParts=3D"1" generateNumberParts=3D"1" catenateWords=3D"0"
> > > catenateNumbers=3D"0" catenateAll=3D"0" splitOnCaseChange=3D"1"/>
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >         <filter class=3D"solr.KeywordMarkerFilterFactory"
> > > protected=3D"protwords.txt"/>
> > >         <filter class=3D"solr.PorterStemFilterFactory"/>
> > >       </analyzer>
> > >     </fieldType>
> > >
> > >     <!-- Less flexible matching, but less false matches.  Probably no=
t
> > > ideal for product names,
> > >          but may be good for SKUs.  Can insert dashes in the wrong
> place
> > > and still match. -->
> > >     <fieldType name=3D"text_en_splitting_tight" class=3D"solr.TextFie=
ld"
> > > positionIncrementGap=3D"100" autoGeneratePhraseQueries=3D"true">
> > >       <analyzer>
> > >         <tokenizer class=3D"solr.WhitespaceTokenizerFactory"/>
> > >         <filter class=3D"solr.SynonymFilterFactory"
> synonyms=3D"synonyms.txt"
> > > ignoreCase=3D"true" expand=3D"false"/>
> > >         <filter class=3D"solr.StopFilterFactory" ignoreCase=3D"true"
> > > words=3D"stopwords_en.txt"/>
> > >         <filter class=3D"solr.WordDelimiterFilterFactory"
> > > generateWordParts=3D"0" generateNumberParts=3D"0" catenateWords=3D"1"
> > > catenateNumbers=3D"1" catenateAll=3D"0"/>
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >         <filter class=3D"solr.KeywordMarkerFilterFactory"
> > > protected=3D"protwords.txt"/>
> > >         <filter class=3D"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=3D"solr.RemoveDuplicatesTokenFilterFactory"/>
> > >       </analyzer>
> > >     </fieldType>
> > >
> > >     <!-- Just like text_general except it reverses the characters of
> > >          each token, to enable more efficient leading wildcard querie=
s.
> > -->
> > >     <fieldType name=3D"text_general_rev" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100">
> > >       <analyzer type=3D"index">
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <filter class=3D"solr.StopFilterFactory" ignoreCase=3D"true"
> > > words=3D"stopwords.txt" enablePositionIncrements=3D"true" />
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >         <filter class=3D"solr.ReversedWildcardFilterFactory"
> > > withOriginal=3D"true"
> > >            maxPosAsterisk=3D"3" maxPosQuestion=3D"2"
> > > maxFractionAsterisk=3D"0.33"/>
> > >       </analyzer>
> > >       <analyzer type=3D"query">
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <filter class=3D"solr.SynonymFilterFactory"
> synonyms=3D"synonyms.txt"
> > > ignoreCase=3D"true" expand=3D"true"/>
> > >         <filter class=3D"solr.StopFilterFactory" ignoreCase=3D"true"
> > > words=3D"stopwords.txt" enablePositionIncrements=3D"true" />
> > >         <filter class=3D"solr.LowerCaseFilterFactory"/>
> > >       </analyzer>
> > >     </fieldType>
> > >
> > >     <!-- charFilter + WhitespaceTokenizer  -->
> > >     <!--
> > >     <fieldType name=3D"text_char_norm" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100" >
> > >       <analyzer>
> > >         <charFilter class=3D"solr.MappingCharFilterFactory"
> > > mapping=3D"mapping-ISOLatin1Accent.txt"/>
> > >         <tokenizer class=3D"solr.WhitespaceTokenizerFactory"/>
> > >       </analyzer>
> > >     </fieldType>
> > >     -->
> > >
> > >     <!-- This is an example of using the KeywordTokenizer along
> > >          With various TokenFilterFactories to produce a sortable fiel=
d
> > >          that does not include some properties of the source text
> > >       -->
> > >     <fieldType name=3D"alphaOnlySort" class=3D"solr.TextField"
> > > sortMissingLast=3D"true" omitNorms=3D"true">
> > >       <analyzer>
> > >         <!-- KeywordTokenizer does no actual tokenizing, so the entir=
e
> > >              input string is preserved as a single token
> > >           -->
> > >         <tokenizer class=3D"solr.KeywordTokenizerFactory"/>
> > >         <!-- The LowerCase TokenFilter does what you expect, which ca=
n
> be
> > >              when you want your sorting to be case insensitive
> > >           -->
> > >         <filter class=3D"solr.LowerCaseFilterFactory" />
> > >         <!-- The TrimFilter removes any leading or trailing whitespac=
e
> > -->
> > >         <filter class=3D"solr.TrimFilterFactory" />
> > >         <!-- The PatternReplaceFilter gives you the flexibility to us=
e
> > >              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://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/package-summary.h=
tml
> > >           -->
> > >         <filter class=3D"solr.PatternReplaceFilterFactory"
> > >                 pattern=3D"([^a-z])" replacement=3D"" replace=3D"all"
> > >         />
> > >       </analyzer>
> > >     </fieldType>
> > >
> > >     <fieldtype name=3D"phonetic" stored=3D"false" indexed=3D"true"
> > > class=3D"solr.TextField" >
> > >       <analyzer>
> > >         <tokenizer class=3D"solr.StandardTokenizerFactory"/>
> > >         <filter class=3D"solr.DoubleMetaphoneFilterFactory"
> > inject=3D"false"/>
> > >       </analyzer>
> > >     </fieldtype>
> > >
> > >     <fieldtype name=3D"payloads" stored=3D"false" indexed=3D"true"
> > > class=3D"solr.TextField" >
> > >       <analyzer>
> > >         <tokenizer class=3D"solr.WhitespaceTokenizerFactory"/>
> > >         <!--
> > >         The DelimitedPayloadTokenFilter can put payloads on tokens...
> for
> > > example,
> > >         a token of "foo|1.4"  would be indexed as "foo" with a payloa=
d
> of
> > > 1.4f
> > >         Attributes of the DelimitedPayloadTokenFilterFactory :
> > >          "delimiter" - a one character delimiter. Default is | (pipe)
> > >          "encoder" - how to encode the following value into a playloa=
d
> > >             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=3D"solr.DelimitedPayloadTokenFilterFactory"
> > > encoder=3D"float"/>
> > >       </analyzer>
> > >     </fieldtype>
> > >
> > >     <!-- lowercases the entire field value, keeping it as a single
> token.
> > > -->
> > >     <fieldType name=3D"lowercase" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100">
> > >       <analyzer>
> > >         <tokenizer class=3D"solr.KeywordTokenizerFactory"/>
> > >         <filter class=3D"solr.LowerCaseFilterFactory" />
> > >       </analyzer>
> > >     </fieldType>
> > >
> > >     <fieldType name=3D"text_path" class=3D"solr.TextField"
> > > positionIncrementGap=3D"100">
> > >       <analyzer>
> > >         <tokenizer class=3D"solr.PathHierarchyTokenizerFactory"/>
> > >       </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=3D"ignored" stored=3D"false" indexed=3D"false"
> > > multiValued=3D"true" class=3D"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=3D"double", then the coordinates would=
 be
> > >         indexed in fields myloc_0___double,myloc_1___double.
> > >       Example: if subFieldSuffix=3D"_d" then the coordinates would be
> > indexed
> > >         in fields myloc_0_d,myloc_1_d
> > >       The subFields are an implementation detail of the fieldType, an=
d
> > end
> > >       users normally should not need to know about them.
> > >      -->
> > >     <fieldType name=3D"point" class=3D"solr.PointType" dimension=3D"2=
"
> > > subFieldSuffix=3D"_d"/>
> > >
> > >     <!-- A specialized field for geospatial search. If indexed, this
> > > fieldType must not be multivalued. -->
> > >     <fieldType name=3D"location" class=3D"solr.LatLonType"
> > > subFieldSuffix=3D"_coordinate"/>
> > >
> > >    <!--
> > >     A Geohash is a compact representation of a latitude longitude pai=
r
> > in a
> > > single field.
> > >     See http://wiki.apache.org/solr/SpatialSearch
> > >    -->
> > >     <fieldtype name=3D"geohash" class=3D"solr.GeoHashField"/>
> > >  </types>
> > >
> > >
> > >  <fields>
> > >
> > >    <field name=3D"_version_" type=3D"long" indexed=3D"true" stored=3D=
"true"/>
> > >    <!-- Valid attributes for fields:
> > >      name: mandatory - the name for the field
> > >      type: mandatory - the name of a previously defined type from the
> > >        <types> section
> > >      indexed: true if this field should be indexed (searchable or
> > sortable)
> > >      stored: true if this field should be retrievable
> > >      multiValued: true if this field may contain multiple values per
> > > document
> > >      omitNorms: (expert) set to true to omit the norms associated wit=
h
> > >        this field (this disables length normalization and index-time
> > >        boosting for the field, and saves some memory).  Only full-tex=
t
> > >        fields or fields that need an index-time boost need norms.
> > >      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.
> > >      default: a value that should be used if no value is specified
> > >        when adding a document.
> > >    -->
> > >         <!-- newspaper-specific fields -->
> > >
> > >         <!-- Unique field  (name of the original one-page PDF file wi=
th
> > no
> > > extention -->
> > >         <field name=3D"id" type=3D"string" indexed=3D"true" stored=3D=
"true"
> > > required=3D"true" />
> > >
> > >         <!-- tdate that the paper was published, like
> > 1997-11-30T00:00:00Z
> > > -->
> > >         <field name=3D"publication_date" type=3D"tdate" indexed=3D"tr=
ue"
> > > stored=3D"true" required=3D"true" />
> > >
> > >         <!-- Integer year that the paper was published -->
> > >         <field name=3D"year" type=3D"int" indexed=3D"true" stored=3D"=
true"
> > > required=3D"true" />
> > >
> > >         <!-- String of the year, like '1998' -->
> > >         <field name=3D"yearstr" type=3D"string" indexed=3D"true"
> stored=3D"true"
> > > required=3D"true" />
> > >
> > >         <!-- Integer of the day of the month (no zero padding)-->
> > >         <field name=3D"day" type=3D"int" indexed=3D"true" stored=3D"t=
rue"
> > > required=3D"true" />
> > >
> > >         <!-- Integer number of the month (no zero padding)-->
> > >         <field name=3D"month_num" type=3D"int" indexed=3D"true" store=
d=3D"true"
> > > required=3D"true" />
> > >
> > >         <!-- Name of month, like 'January'-->
> > >         <field name=3D"month" type=3D"string" indexed=3D"true" stored=
=3D"true"
> > > required=3D"true" />
> > >
> > >         <!-- name of the publication, i.e., Battle Creek Enquirer -->
> > >         <field name=3D"publication_name" type=3D"string" indexed=3D"t=
rue"
> > > stored=3D"true" required=3D"true" />
> > >
> > >         <!-- Short name of the publication, i.e., battlecreekenquirer
> -->
> > >         <field name=3D"short_name" type=3D"string" indexed=3D"true"
> > stored=3D"true"
> > > required=3D"true" />
> > >
> > >         <!-- Image number (roughly page number, no zero padding, will
> > match
> > > last 3 digits of filename) -->
> > >         <field name=3D"image_number" type=3D"int" indexed=3D"true"
> > stored=3D"true"
> > > required=3D"true" />
> > >
> > >         <!-- Name of the PDF file (just the filename, no path) -->
> > >         <field name=3D"filename" type=3D"string" indexed=3D"true"
> stored=3D"true"
> > > required=3D"true" />
> > >
> > >         <!-- Copyright Restricted (not allowed outside willard networ=
ks
> > > values: yes, no) -->
> > >         <field name=3D"copyright_restricted" type=3D"string" indexed=
=3D"true"
> > > stored=3D"true" required=3D"true" />
> > >
> > >         <!-- Copyright Year (copyright cut off) -->
> > >         <field name=3D"copyright_year" type=3D"string" indexed=3D"tru=
e"
> > > stored=3D"true" required=3D"true" />
> > >
> > >         <!-- Publication Type (newspaper or shopper) -->
> > >         <field name=3D"publication_type" type=3D"string" indexed=3D"t=
rue"
> > > stored=3D"true" required=3D"true" />
> > >
> > >         <!-- Publication Text -->
> > >         <field name=3D"publication_text" type=3D"string" indexed=3D"t=
rue"
> > > stored=3D"true" required=3D"true" multiValued=3D"true"/>
> > >
> > >         <!-- end newspaper-specific fields -->
> > >
> > >    <field name=3D"sku" type=3D"text_en_splitting_tight" indexed=3D"tr=
ue"
> > > stored=3D"true" omitNorms=3D"true"/>
> > >    <field name=3D"name" type=3D"text_general" indexed=3D"true"
> stored=3D"true"/>
> > >    <field name=3D"alphaNameSort" type=3D"alphaOnlySort" indexed=3D"tr=
ue"
> > > stored=3D"false"/>
> > >    <field name=3D"manu" type=3D"text_general" indexed=3D"true" stored=
=3D"true"
> > > omitNorms=3D"true"/>
> > >    <field name=3D"cat" type=3D"string" indexed=3D"true" stored=3D"tru=
e"
> > > multiValued=3D"true"/>
> > >    <field name=3D"features" type=3D"text_general" indexed=3D"true"
> > stored=3D"true"
> > > multiValued=3D"true"/>
> > >    <field name=3D"includes" type=3D"text_general" indexed=3D"true"
> > stored=3D"true"
> > > termVectors=3D"true" termPositions=3D"true" termOffsets=3D"true" />
> > >
> > >    <field name=3D"weight" type=3D"float" indexed=3D"true" stored=3D"t=
rue"/>
> > >    <field name=3D"price"  type=3D"float" indexed=3D"true" stored=3D"t=
rue"/>
> > >    <field name=3D"popularity" type=3D"int" indexed=3D"true" stored=3D=
"true" />
> > >    <field name=3D"inStock" type=3D"boolean" indexed=3D"true" stored=
=3D"true" />
> > >
> > >    <!--
> > >    The following store examples are used to demonstrate the various
> ways
> > > one might _CHOOSE_ to
> > >     implement spatial.  It is highly unlikely that you would ever hav=
e
> > ALL
> > > of these fields defined.
> > >     -->
> > >    <field name=3D"store" type=3D"location" indexed=3D"true" stored=3D=
"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 retu=
rn
> > >      multiple values for them.
> > >    -->
> > >    <field name=3D"title" type=3D"text_general" indexed=3D"true" store=
d=3D"true"
> > > multiValued=3D"true"/>
> > >    <field name=3D"subject" type=3D"text_general" indexed=3D"true"
> > stored=3D"true"/>
> > >    <field name=3D"description" type=3D"text_general" indexed=3D"true"
> > > stored=3D"true"/>
> > >    <field name=3D"comments" type=3D"text_general" indexed=3D"true"
> > > stored=3D"true"/>
> > >    <field name=3D"author" type=3D"text_general" indexed=3D"true"
> > stored=3D"true"/>
> > >    <field name=3D"keywords" type=3D"text_general" indexed=3D"true"
> > > stored=3D"true"/>
> > >    <field name=3D"category" type=3D"text_general" indexed=3D"true"
> > > stored=3D"true"/>
> > >    <field name=3D"content_type" type=3D"string" indexed=3D"true"
> stored=3D"true"
> > > multiValued=3D"true"/>
> > >    <field name=3D"last_modified" type=3D"date" indexed=3D"true"
> stored=3D"true"/>
> > >    <field name=3D"links" type=3D"string" indexed=3D"true" stored=3D"t=
rue"
> > > multiValued=3D"true"/>
> > >
> > >
> > >    <!-- catchall field, containing all other searchable text fields
> > > (implemented
> > >         via copyField further on in this schema  -->
> > >    <field name=3D"text" type=3D"text_general" indexed=3D"true" stored=
=3D"true"
> > > multiValued=3D"true"/>
> > >
> > >    <!-- catchall text field that indexes tokens both normally and in
> > > reverse for efficient
> > >         leading wildcard queries. -->
> > >    <field name=3D"text_rev" type=3D"text_general_rev" indexed=3D"true=
"
> > > stored=3D"false" multiValued=3D"true"/>
> > >
> > >    <!-- non-tokenized version of manufacturer to make it easier to so=
rt
> > or
> > > group
> > >         results by manufacturer.  copied from "manu" via copyField --=
>
> > >    <field name=3D"manu_exact" type=3D"string" indexed=3D"true"
> stored=3D"false"/>
> > >
> > >    <field name=3D"payloads" type=3D"payloads" indexed=3D"true"
> stored=3D"true"/>
> > >
> > >    <!-- Uncommenting the following will create a "timestamp" field
> using
> > >         a default value of "NOW" to indicate when each document was
> > > indexed.
> > >      -->
> > >    <!--
> > >    <field name=3D"timestamp" type=3D"date" indexed=3D"true" stored=3D=
"true"
> > > default=3D"NOW" multiValued=3D"false"/>
> > >      -->
> > >
> > >
> > >    <!-- Dynamic field definitions.  If a field name is not found,
> > > dynamicFields
> > >         will be used if the name matches any of the patterns.
> > >         RESTRICTION: the glob-like pattern in the name attribute must
> > have
> > >         a "*" only at the start or the end.
> > >         EXAMPLE:  name=3D"*_i" will match any field ending in _i (lik=
e
> > > myid_i, z_i)
> > >         Longer patterns will be matched first.  if equal size pattern=
s
> > >         both match, the first appearing in the schema will be used.
> -->
> > >    <dynamicField name=3D"*_i"  type=3D"int"    indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_s"  type=3D"string"  indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_l"  type=3D"long"   indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_t"  type=3D"text_general"    indexed=3D"tr=
ue"
> > > stored=3D"true"/>
> > >    <dynamicField name=3D"*_txt" type=3D"text_general"    indexed=3D"t=
rue"
> > > stored=3D"true" multiValued=3D"true"/>
> > >    <dynamicField name=3D"*_b"  type=3D"boolean" indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_f"  type=3D"float"  indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_d"  type=3D"double" indexed=3D"true"
> > stored=3D"true"/>
> > >
> > >    <!-- Type used to index the lat and lon components for the
> "location"
> > > FieldType -->
> > >    <dynamicField name=3D"*_coordinate"  type=3D"tdouble" indexed=3D"t=
rue"
> > > stored=3D"false"/>
> > >
> > >    <dynamicField name=3D"*_dt" type=3D"date"    indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_p"  type=3D"location" indexed=3D"true"
> > stored=3D"true"/>
> > >
> > >    <!-- some trie-coded dynamic fields for faster range queries -->
> > >    <dynamicField name=3D"*_ti" type=3D"tint"    indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_tl" type=3D"tlong"   indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_tf" type=3D"tfloat"  indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_td" type=3D"tdouble" indexed=3D"true"
> > stored=3D"true"/>
> > >    <dynamicField name=3D"*_tdt" type=3D"tdate"  indexed=3D"true"
> > stored=3D"true"/>
> > >
> > >
> > >    <dynamicField name=3D"ignored_*" type=3D"ignored" multiValued=3D"t=
rue"/>
> > >    <dynamicField name=3D"attr_*" type=3D"text_general" indexed=3D"tru=
e"
> > > stored=3D"true" multiValued=3D"true"/>
> > >
> > >    <dynamicField name=3D"random_*" type=3D"random" />
> > >
> > >    <!-- uncomment the following to ignore any fields that don't alrea=
dy
> > > match an existing
> > >         field name or dynamic field, rather than reporting them as an
> > > error.
> > >         alternately, change the type=3D"ignored" to some other type e=
.g.
> > > "text" if you want
> > >         unknown fields indexed and/or stored by default -->
> > >    <!--dynamicField name=3D"*" type=3D"ignored" multiValued=3D"true" =
/-->
> > >
> > >  </fields>
> > >
> > >  <!-- Field to use to determine and enforce document uniqueness.
> > >       Unless this field is marked with required=3D"false", it will be=
 a
> > > required field
> > >    -->
> > >  <uniqueKey>id</uniqueKey>
> > >
> > >  <!-- field for the QueryParser to use when an explicit fieldname is
> > absent
> > > -->
> > >  <defaultSearchField>text</defaultSearchField>
> > >
> > >  <!-- SolrQueryParser configuration: defaultOperator=3D"AND|OR" -->
> > >  <solrQueryParser defaultOperator=3D"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=3D"cat" dest=3D"text"/>
> > >    <copyField source=3D"name" dest=3D"text"/>
> > >    <copyField source=3D"manu" dest=3D"text"/>
> > >    <copyField source=3D"features" dest=3D"text"/>
> > >    <copyField source=3D"includes" dest=3D"text"/>
> > >    <copyField source=3D"manu" dest=3D"manu_exact"/>
> > >    <copyField source=3D"publication_text" dest=3D"text" />
> > >    <!-- 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=3D"*_t" dest=3D"text" maxChars=3D"300000000"/>
> > >
> > >    <!-- copy name to alphaNameSort, a field designed for sorting by
> name
> > > -->
> > >    <!-- <copyField source=3D"name" dest=3D"alphaNameSort"/> -->
> > >
> > >
> > >  <!-- Similarity is the scoring routine for each document vs. a query=
.
> > >       A custom similarity may be specified here, but the default is
> fine
> > >       for most applications.  -->
> > >  <!-- <similarity class=3D"org.apache.lucene.search.DefaultSimilarity=
"/>
> > -->
> > >  <!-- ... OR ...
> > >       Specify a SimilarityFactory class name implementation
> > >       allowing parameters to be used.
> > >  -->
> > >  <!--
> > >  <similarity class=3D"com.example.solr.CustomSimilarityFactory">
> > >    <str name=3D"paramkey">param value</str>
> > >  </similarity>
> > >  -->
> > >
> > >
> > > </schema>
> > >
> > >
> > >
> > >
> > >
> > > On Sat, Jun 27, 2015 at 11:27 AM, Erick Erickson <
> > erickerickson@gmail.com>
> > > wrote:
> > >
> > > > This should be no different in 5.2 than 4.6.
> > > >
> > > > My first guess is a typo somewhere or some similar forehead-slapper=
.
> > > > Are you sure you're specifying the field in the "fl" list?
> > > >
> > > > Take a look at the index files, the *.fdt files are where the store=
d
> > data
> > > > goes. You can't look into them, but for the same documents they
> should
> > > > be roughly the same aggregate size as they are in 4.6
> > > > 'du -hc *.fdt' will sum them all up for you (*nix).
> > > >
> > > > Second thing I'd do for sanity check is tail out the Solr log while
> > > > indexing and querying, just to see "stuff" go by and see if any
> > > > errors are thrown, although it sounds like you wouldn't see
> > > > any search results at all if there was something wrong with
> > > > indexing.
> > > >
> > > > And if none of that sheds any light, let's see the schema file?
> > > > Maybe the results of adding &debug=3Dall to the query?
> > > >
> > > > Best,
> > > > Erick
> > > >
> > > > On Fri, Jun 26, 2015 at 8:05 AM, Mark Ehle <markehle@gmail.com>
> wrote:
> > > > > In my schema from 4.6, the text was in the 'text' field, and the
> > > "stored"
> > > > > attrib was set to "true" as it is in the 5.2 schema. I am ingesti=
ng
> > the
> > > > > text from files on the server , and it used to work just fine wit=
h
> > > 4.6. I
> > > > > am using the same schema except I had to get rid the field types
> > pint,
> > > > > plong, pfloat, pdouble and pdate. Otherwise, the schema is
> identical.
> > > > >
> > > > > How do I tell SOLR 5.2 to store the text from a file to a certain
> > > field?
> > > > >
> > > > > Thanks!
> > > > >
> > > > >
> > > > > On Fri, Jun 26, 2015 at 7:29 AM, Alessandro Benedetti <
> > > > > benedetti.alex85@gmail.com> wrote:
> > > > >
> > > > >> Actually storing or not storing a field is a simple schema.xml
> > > > >> configuration.
> > > > >> This suggestion can be obvious, but =E2=80=A6 have you checked y=
ou have
> your
> > > > >> "stored" attribute set "true" for the field you are interested ?
> > > > >>
> > > > >> I am talking about the 5.2 schema.
> > > > >>
> > > > >> Cheers
> > > > >>
> > > > >> 2015-06-26 12:24 GMT+01:00 Mark Ehle <markehle@gmail.com>:
> > > > >>
> > > > >> > Folks -
> > > > >> >
> > > > >> > I am using SOLR 4.6 to run a newspaper indexing site we have a=
t
> > the
> > > > >> library
> > > > >> > I work at. I would like to update to 5.2, and I have an instan=
ce
> > of
> > > it
> > > > >> > running. When I go to index the txt files of each newspaper
> page,
> > I
> > > > can
> > > > >> > search and find stuff, but there is no text stored any more. I
> do
> > > use
> > > > >> > highlighting so I need the text there.
> > > > >> >
> > > > >> > What would be different about 5.2 that would account for this?
> > > > >> >
> > > > >> > Thanks!
> > > > >> >
> > > > >> > Mark Ehle
> > > > >> > Computer Support Librarian
> > > > >> > Willard Library
> > > > >> > Battle Creek,MI
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> --------------------------
> > > > >>
> > > > >> Benedetti Alessandro
> > > > >> Visiting card : http://about.me/alessandro_benedetti
> > > > >>
> > > > >> "Tyger, tyger burning bright
> > > > >> In the forests of the night,
> > > > >> What immortal hand or eye
> > > > >> Could frame thy fearful symmetry?"
> > > > >>
> > > > >> William Blake - Songs of Experience -1794 England
> > > > >>
> > > >
> > >
> >
> >
> >
> > --
> > --------------------------
> >
> > Benedetti Alessandro
> > Visiting card : http://about.me/alessandro_benedetti
> >
> > "Tyger, tyger burning bright
> > In the forests of the night,
> > What immortal hand or eye
> > Could frame thy fearful symmetry?"
> >
> > William Blake - Songs of Experience -1794 England
> >
>


--=20
--------------------------

Benedetti Alessandro
Visiting card : http://about.me/alessandro_benedetti

"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"

William Blake - Songs of Experience -1794 England

--047d7b3a9cb02d44880519be7534--