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

Fix Cassandra Range pushdown #8629

Merged

Commits on Aug 3, 2021

  1. Configuration menu
    Copy the full SHA
    208cf92 View commit details
    Browse the repository at this point in the history

Commits on Aug 9, 2021

  1. Fix Cassandra OrderedRangeSet pushdown

    Due to the fact that Cassandra supports only
    =, <, >, ....
    IN (....)
    ... AND ...
    
    When we have single single-valued range, we use =.
    When we have single range, we use low bound < x AND x < high bound (or <= when appropriate)
    When we have multiple single-valued range, we use IN (...).
    In all other cases, including when IN is not supported in Cassandra,
    we push down min/max bounds (domain.getValues().getRanges().getSpan())
    using low bound < x AND x < high bound (or <= when appropriate)
    s2lomon committed Aug 9, 2021
    Configuration menu
    Copy the full SHA
    33ef97b View commit details
    Browse the repository at this point in the history