Sannier Elodie created SOLR-4866:
------------------------------------

             Summary: 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to