lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ronald Matamoros <RMatamo...@searchtechnologies.com>
Subject SolrCloud: facet range option f.<field>.facet.mincount=1 omits buckets on response
Date Tue, 27 May 2014 15:25:04 GMT
Good afternoon,

Is the f.<field>.facet.mincount option supported on a distributed search?
Under SolrCloud experiencing that some buckets are ignored when using the option "f.<field>.facet.mincount=1".

The Solr logs do not indicate any error or warning during execution.
The debug=true option and increasing the log levels to the FacetComponent do not provide any
hints to the behaviour.

Replicated the issue on both Solr 4.5.1 & 4.8.1.
Attached a PDF that provides additional details and steps to replicate the behaviour using
the out of the box Solr distribution.

Any insight or recommendation to tackle this situation is much appreciated.

Example, 

      Removing the f.<field>.facet.mincount=1 option gives the expected list of buckets
for the 6 documents matched.

        <lst name="facet_ranges">
         <lst name="price">
           <lst name="counts">
             <int name="0.0">0</int>
             <int name="50.0">1</int>
             <int name="100.0">0</int>
             <int name="150.0">3</int>
             <int name="200.0">0</int>
             <int name="250.0">1</int>
             <int name="300.0">0</int>
             <int name="350.0">0</int>
             <int name="400.0">0</int>
             <int name="450.0">0</int>
             <int name="500.0">0</int>
             <int name="550.0">0</int>
             <int name="600.0">0</int>
             <int name="650.0">0</int>
             <int name="700.0">0</int>
             <int name="750.0">1</int>
             <int name="800.0">0</int>
             <int name="850.0">0</int>
             <int name="900.0">0</int>
             <int name="950.0">0</int>
           </lst>
           <float name="gap">50.0</float>
           <float name="start">0.0</float>
           <float name="end">1000.0</float>
           <int name="before">0</int>
           <int name="after">0</int>
           <int name="between">2</int>
         </lst>
       </lst>

      Using the f.<field>.facet.mincount=1 option removes the 0 count buckets but will
also omit bucket <int name="250.0">

       <lst name="facet_ranges">
          <lst name="price">
            <lst name="counts">
                <int name="50.0">1</int>
                <int name="150.0">3</int>
                <int name="750.0">1</int>
             </lst>
             <float name="gap">50.0</float>
             <float name="start">0.0</float>
             <float name="end">1000.0</float>
             <int name="before">0</int>
             <int name="after">0</int>
             <int name="between">4</int>
          </lst>
        </lst>

     Refreshing the query using the browser's F5 option renders a different bucket list 
     (you may need to refresh multiple times)

       <lst name="facet_ranges">
          <lst name="price">
            <lst name="counts">
                <int name="150.0">3</int>
                <int name="250.0">1</int>
             </lst>
             <float name="gap">50.0</float>
             <float name="start">0.0</float>
             <float name="end">1000.0</float>
             <int name="before">0</int>
             <int name="after">0</int>
             <int name="between">2</int>
          </lst>
        </lst>

Regards 
Ronald Matamoros

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message