You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2013/06/12 21:10:20 UTC
[jira] [Commented] (SOLR-4866) FieldCache insanity with field used
as facet and group
[ https://issues.apache.org/jira/browse/SOLR-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681525#comment-13681525 ]
Hoss Man commented on SOLR-4866:
--------------------------------
bq. I'm reproducing the problem with the 4.2.1 example with 2 shards.
Elode, awesome -- thank you for helping figure out how to reproduce this.
Yes, the crux of hte problem seems to be exclusively with doing distributed searching. specifically...
* Faceting using the fc or fcs methods, regardless of wether it's a single node or a distributed search, uses the basic type array based FieldCache for the field you are faceting on (ie: "IntsFromArray" for popularity)
* Grouping uses two different types of FieldCaches depending on whether you are doing a single node grouping request, or the more complicated multi-phase distributed grouping request:
** single node: type based array
** distributed: SortedDocValues
I'm not totally familiar with the grouping code, but I didn't see any obvious indication that this way a "mistake" ... I think this is an example of the type of situation where we different data is needed for the two different grouping algorithms and it means accepting some "insane" redundancy
> FieldCache insanity with field used as facet and group
> ------------------------------------------------------
>
> Key: SOLR-4866
> URL: https://issues.apache.org/jira/browse/SOLR-4866
> Project: Solr
> Issue Type: Bug
> Reporter: Sannier Elodie
> Priority: Minor
>
> I am using the Lucene FieldCache with SolrCloud 4.2.1 and I have "insane" instances for a field used as facet and group field.
> schema fieldType & filed declaration for my
> merchantid field :
> <fieldType name="int" class="solr.TrieIntField" precisionStep="0" sortMissingLast="true" omitNorms="true" positionIncrementGap="0"/>
> <field name="merchantid" type="int" indexed="true" stored="true" required="true"/>
> The mbean stats output shows the field cache insanity after executing queries like :
> /select?q=*:*&facet=true&facet.field=merchantid
> /select?q=*:*&group=true&group.field=merchantid
> <int name="insanity_count">25</int>
> <str name="insanity#0">VALUEMISMATCH: Multiple distinct value objects for SegmentCoreReader(owner=_1z1(4.2.1):C3916)+merchantid
> 'SegmentCoreReader(owner=_1z1(4.2.1):C3916)'=>'merchantid',class org.apache.lucene.index.SortedDocValues,0.5=>org.apache.lucene.search.FieldCacheImpl$SortedDocValuesImpl#1517585400
> 'SegmentCoreReader(owner=_1z1(4.2.1):C3916)'=>'merchantid',int,org.apache.lucene.search.FieldCache.NUMERIC_UTILS_INT_PARSER=>org.apache.lucene.search.FieldCacheImpl$IntsFromArray#781169939
> 'SegmentCoreReader(owner=_1z1(4.2.1):C3916)'=>'merchantid',int,null=>org.apache.lucene.search.FieldCacheImpl$IntsFromArray#781169939
> </str>
> ...
> see http://markmail.org/thread/7gctyh6vn3eq5jso
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org