Sander wrote: > When selecting a few of those facets `fq=releasedate:2005 OR > releasedate:2007 OR releasedate:2009` (here not urlencoded for legibility) > everything works as expected > > However, when I add the 17th (16+1!) year like that, suddenly I don't get > any results. I see that the debug output in parsed_filter_queries has > changed drastically, from > `IntersectsPrefixTreeQuery(IntersectsPrefixTreeQuery(fieldName=releasedate,queryShape=2005,detailLevel=9,prefixGridScanLevel=8))` > x16 to `TermInSetQuery(releasedate:(2005 2007 2009 2011 2012 2013 2014 2015 > 2016 2017 2018 2019 2020 2021 2022 2023 2024))` > > I'd like to know if > 2) there is anything (in configuration) I can do to prevent this > optimization (?) from happening to work around the bug?
For that future searcher who'll stumble upon this with the same problem, I've settled on changing my query to `fq=releasedate:[2005-01 TO 2005-12] OR releasedate:[2007-01 TO 2007-12] OR ...` as the least inelegant workaround. This syntax generates the same `IntersectsPrefixTreeQuery(IntersectsPrefixTreeQuery(fieldName=releasedate,queryShape=2005,detailLevel=9,prefixGridScanLevel=8))` parsed query, but then keeps adding more of the same after the 16th (and 32nd) term. ~ Sander
