Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Range Queries are not working #159

Open
mithranalandur opened this issue Dec 10, 2017 · 2 comments
Open

Range Queries are not working #159

mithranalandur opened this issue Dec 10, 2017 · 2 comments

Comments

@mithranalandur
Copy link

Hi I tried overriding getRangeQuery() but still having the same issue.

I tried debugging and i am seeing response as [query1,query3] instead of [query1]

The IndexSearcher query is "title:test1 __anytokenfield:ANYTOKEN" used inside the monitor query. i.e., QueryIndex.java line 110. instead of "title:test1 upvote:[12 TO 2147483647]"

I got [query1, query3] as response the complete code is at
https://gist.github.com/mithranalandur/ce170ce287eca2a8f2cfaab6342068df

Can you give me some pointer like where am i going wrong.

@romseygeek
Copy link
Collaborator

That's what I'd expect. The TermFilteredPresearcher doesn't know anything about point queries, so if it comes across a query that only contains a point range query, it will run it against all input documents.

The plan is at some point to implement a Points-aware presearcher that will use LongRange or DoubleRange to index exact point queries.

@ZronekM
Copy link

ZronekM commented Jan 26, 2023

Has this issue been resolved somehow? I am also currently struggling to make rangequeries for the presearcher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants