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

Resolves #1691: Lucene negative queries #1694

Merged
merged 3 commits into from Jun 3, 2022
Merged

Resolves #1691: Lucene negative queries #1694

merged 3 commits into from Jun 3, 2022

Commits on Jun 3, 2022

  1. Resolves FoundationDB#1674: Lucene scans without queries

    @MMcM
    MMcM committed Jun 3, 2022
    Configuration menu
    Copy the full SHA
    c605c18 View commit details
    Browse the repository at this point in the history

  2. Resolves FoundationDB#1691: Lucene negative queries 

    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
    MMcM committed Jun 3, 2022
    Configuration menu
    Copy the full SHA
    410a9f5 View commit details
    Browse the repository at this point in the history

  3. Try to make that clearer by using switch instead of if.

    @MMcM
    MMcM committed Jun 3, 2022
    Configuration menu
    Copy the full SHA
    2d8ddd8 View commit details
    Browse the repository at this point in the history