Markus,
Can you pick up one of the values in the facets and try running query using
that. Ideally numFound should match the facet count. If those aren't
matching I guess your index is still sorta damaged but you aren't really
noticing it.
On Sep 15, 2016 4:44 AM, "Markus Jelsma" <markus.jel...@openindex.io> wrote:
> Mikhail - yes, there are results for the query. The set is empty as if
> there are no values for the field, {}.
>
> Everything checked out correctly but no facet results, until immediately
> after the optimize.
>
> Thanks,
> Markus
>
> -----Original message-----
> > From:Mikhail Khludnev <m...@apache.org>
> > Sent: Thursday 15th September 2016 10:12
> > To: solr-user <solr-user@lucene.apache.org>
> > Subject: Re: Facetting on a field doesn't work, until i optimized the
> index
> >
> > Markus,
> >
> > Could you spot more details about this particular field type? How does
> > 'empty set of facets' look like? Is there results in that query?
> >
> > On Wed, Sep 14, 2016 at 4:15 PM, Markus Jelsma <
> markus.jel...@openindex.io>
> > wrote:
> >
> > > Hello - we've just spotted the weirdest issue on Solr 6.1.
> > >
> > > We have a Solr index full of logs, new items are added every few
> minutes.
> > > We also have an application that shows charts based on what's in the
> index,
> > > Banana style.
> > >
> > > Yesterday we saw facets for a specific field were missing. Today we
> > > checked it out until we reduced the facet query just to
> > > facet=true&facet.field=FIELD, but it returned nothing of use, just an
> empty
> > > set of facets.
> > >
> > > My colleague suggested the crazy idea to optimize the index, i
> protested
> > > because it is no use, numDoc always equals maxDoc and the optimize
> button
> > > was missing anyway. So i forced an optimize via the URL, and it
> worked, the
> > > facets for that field are now back!
> > >
> > > Any ideas? Is there a related ticket?
> > >
> > > Thanks,
> > > Markus
> > >
> >
> >
> >
> > --
> > Sincerely yours
> > Mikhail Khludnev
> >
>
