I did a little git spelunking and found this PR https://github.com/apache/lucene-solr/pull/794 where it was introduced. It does sound to me as if the intent was to match on multiple multi-dimensional ranges (ie hypercubes), not on any dimension among multiple ranges? Why would anyone ever want to do that? On the other hand a lot of people looked at it ... so maybe we're missing something here?
On Sun, Nov 21, 2021 at 11:14 AM Greg Miller <gsmil...@gmail.com> wrote: > > Hi folks- > > Is anyone familiar with MultiRangeQuery (found in > o.a.l.sandbox.search)? I was playing around with it recently since it > might be a good fit for a use-case I'm working on for Amazon's Product > Search engine, but it looks like it has a pretty fundamental bug in > how it works. That or I'm completely mis-understanding what the query > is meant to do. > > My understanding is that this query should consider documents to be a > match if they contain a point that is found in _any_ of the ranges > represented by this query (i.e., it's a disjunction over a set of > query ranges). But... it appears that the query incorrectly considers > a document to be a match if its point matches on any single dimension > of any range (where it should be requiring all dimensions in a > particular range to match). > > I added a unit test to demonstrate this bug along with a proposed fix > over here: https://github.com/apache/lucene/pull/437 > > If anyone is familiar with this query (or better yet, uses it), I'd be > really interested in your input. > > Cheers, > -Greg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
