[13.0.x] ISPN-13454 Ickle DELETE should not allow usage of Query.startOffset/maxResults #9650
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…axResults * also prevent use of projections with Query.entryIterator() because projecting anything other than key and value would work against the purpose of entryIterator * use proper i18n for some newly added exceptions * prefer throwing CacheException in case of api misusage instead of other less specific RuntimeExceptions
|
@tristantarrant Can this be merged in 13.0.x ? Or is it too late (or too soon) ? |
|
Too soon. We will unfreeze 13.0.x soon |
|
Merged, thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
projecting anything other than key and value would work against the
purpose of entryIterator
https://issues.redhat.com/browse/ISPN-13454