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

[TRACKING ISSUE] Ability to specify multiple partitions in a predicate query (redux) #552

Open
1 of 6 tasks
hz-devops-test opened this issue May 11, 2022 · 0 comments
Open
1 of 6 tasks

Comments

@hz-devops-test
Copy link

The tracking issue for the Java side PR.

See hazelcast/hazelcast#21319 for details.


This is a redux of PR-18171. I'm continuing on from @ashley-taylor.

I've gone with a slightly different approach of making a backwards compatible change to the existing PartitionPredicate interface (instead of making an entirely new interface). This seemed lower risk as existing code with single partition keys will continue to work, while anything new can take advantage of the getPartitionKeys method.

Breaking changes (list specific methods/types/messages):

  • PartitionPredicateImpl constructor

Checklist:

  • Labels (Team:, Type:, Source:, Module:) and Milestone set
  • Label Add to Release Notes or Not Release Notes content set
  • Request reviewers if possible
  • Send backports/forwardports if fix needs to be applied to past/future releases
  • New public APIs have @Nonnull/@Nullable annotations
  • New public APIs have @since tags in Javadoc
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

1 participant