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.

Sign up for GitHub

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

Jump to bottom

Lucene negative queries #1691

Closed
MMcM opened this issue May 24, 2022 · 0 comments
Closed

Lucene negative queries #1691

MMcM opened this issue May 24, 2022 · 0 comments
Assignees
@MMcM
Labels
enhancement New feature or request

Comments

@MMcM
Copy link
Contributor

MMcM commented May 24, 2022

Queries with Query.not should generate appropriate Querys, trying to avoid introducing a wildcard when possible.
@MMcM MMcM self-assigned this May 24, 2022
@MMcM MMcM added the enhancement New feature or request label May 24, 2022
MMcM added a commit to MMcM/fdb-record-layer that referenced this issue May 24, 2022
@MMcM
Resolves FoundationDB#1691: Lucene negative queries
70948fd
MMcM added a commit to MMcM/fdb-record-layer that referenced this issue May 25, 2022
@MMcM
Resolves FoundationDB#1691: Lucene negative queries
942fb51 
At root a new clause class that produces a negated boolean.
But since Lucene represents that as another Occur, the clause actually implements set subtraction.
The planner tries to maximize the cases where the subtraction is from a positive query rather than just *:*.
MMcM added a commit to MMcM/fdb-record-layer that referenced this issue May 25, 2022
@MMcM
Resolves FoundationDB#1691: Lucene negative queries
42daece 
At root a new clause class that produces a negated boolean.
But since Lucene represents that as another Occur, the clause actually implements set subtraction.
The planner tries to maximize the cases where the subtraction is from a positive query rather than just *:*.
MMcM added a commit to MMcM/fdb-record-layer that referenced this issue May 31, 2022
@MMcM
Resolves FoundationDB#1691: Lucene negative queries
4d7fe10 
At root a new clause class that produces a negated boolean.
But since Lucene represents that as another Occur, the clause actually implements set subtraction.
The planner tries to maximize the cases where the subtraction is from a positive query rather than just *:*.
alecgrieser added a commit that referenced this issue Jun 3, 2022
@alecgrieser
Merge pull request #1694 from MMcM/lucene-not-query
d86feac 
Resolves #1691: Lucene negative queries
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MMcM MMcM

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MMcM