Here are the field definitions for both our old and new index... as you can see
that are identical. We've been using this chain and field type starting with
Solr 1.4 and never had any problem. As for the documents, both indexes are
using the same data source. They could be slightly out of sync from time to
time but we tend to index them on a daily basis. Both indexes are also using
the same code (indexing through SolrJ) to index their content.
The source is a column in MySql that contains entries such as "4,1" that get
stored in a Multivalued fields after replacing commas by spaces
OLD (4.6.1):
<fieldType name="text_ws" class="solr.TextField" positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
</analyzer>
</fieldType>
<field name="ad_job_type_id" type="text_ws" indexed="true" stored="true"
required="false" multiValued="true" />
NEW (4.7.1):
<fieldType name="text_ws" class="solr.TextField" positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
</analyzer>
</fieldType>
<field name="ad_job_type_id" type="text_ws" indexed="true" stored="true"
required="false" multiValued="true" />
It looks like the /analysis/field hanlder is not active in our current setup. I
will look into this and perform additional checks later as we are currently
doing a full reindex of our DB.
Thanks for your time
> -----Original Message-----
> From: Shawn Heisey [mailto:s...@elyograg.org]
> Sent: April-09-14 5:23 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Were changes made to facetting on multivalued fields recently?
>
> On 4/9/2014 2:15 PM, Erick Erickson wrote:
> > Right, but the response in the doc when you make a request is almost,
> > but not quite totally, unrelated to how facet values are tallied. It's
> > all about what tokens are actually in your index, which you can see in
> > the "schema browser"...
>
> Supplement to what Erick has told you:
>
> SOLR-5512 seems to be related to facets using docValues. The commit for
> that issue looks like it only touches on that specifically.If you do not have
> (and never have had) docValues on this field, then SOLR-5512 should not
> apply.
>
> I am reasonably sure that for facets on fields with docValues, your facets
> would reflect the *stored* information, not the indexed information.
>
> Finally, I don't think that docValues work on fieldtypes whose class is
> solr.TextField, which is the only class that can have an analysis chain that
> would turn "4 5 1" into three separate tokens. The response that you shared
> where the value is "4 5 1" looks like there is only one value in the field --
> so
> for that document, it is effectively the same as one that is single-valued.
>
> Bottom line: It looks like either your analysis chain is working differently
> in
> the newer version, or you have documents in your newer index that are not
> in the older one. Can you share the field and fieldType definitions from both
> versions? Did your luceneMatchVersion change with the upgrade? If you are
> using DIH to populate your index, can you also share your DIH config?
>
> Thanks,
> Shawn
>
>
> -----
> Aucun virus trouvé dans ce message.
> Analyse effectuée par AVG - www.avg.fr
> Version: 2014.0.4354 / Base de données virale: 3722/7256 - Date:
> 27/03/2014 La Base de données des virus a expiré.
