Re: OR query for 16+ values in daterange field gets parsed as TermInSetQuery, leading to no results

2025-03-28 Thread Sander
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

OR query for 16+ values in daterange field gets parsed as TermInSetQuery, leading to no results

2025-03-27 Thread Sander
ase) I'm possibly overlooking something basic and stupid which could explain and 'fix' this? Thanks in advance! ~ Sander