-
Notifications
You must be signed in to change notification settings - Fork 74
Support for Paging Predicate implementation #212
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
Conversation
|
Can one of the admins verify this patch? |
|
verify |
mdumandag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yagmurdulger Thanks for the great effort. This PR looks good.
I finished my first round of review and left some comments. Could you take a look at them?
|
@mdumandag Thank you very much for the review! I have changed the PR based on your comments and marked them as resolved. There are still a few questions remaining, could you take a look at them? |
|
@mdumandag Thanks for your feedback! PR is ready for another round of review. |
|
Thanks for the changes @yagmurdulger. I will go over it again |
mdumandag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yagmurdulger sorry for the late response, I went over the PR again. It looks pretty good now. I have some further comments and questions.
|
verify |
|
Hi @mdumandag . Thanks a lot for the second round of review! I have improved the PR based on your suggestions. |
|
verify |
|
Can one of the admins verify this patch? |
1 similar comment
|
Can one of the admins verify this patch? |
This is the port of hazelcast#212 to the 4.0 branch. However, there are some differences from that PR. - Documentation of the feature is a little bit different since the client side sorting is removed. - Tests are more-or-less ported directly with a few additions for input validations. However, the above PR was using `six.assertCounEqual` for assertions which checks equality but not order. For paging predicate tests, it makes more sense to check ordering. - Client side codecs and holder classes for PagingPredicates and AnchorDataLists are added. - Some public methods, like `get_anchor`, `set_anchor`, `get_nearest_anchor_entry` is removed. `get_anchor` is defined on the public API on the Java side but I think it does not provide any functionality to the user.
This is the port of hazelcast#212 to the 4.0 branch. However, there are some differences from that PR. - Documentation of the feature is a little bit different since the client side sorting is removed. - Tests are more-or-less ported directly with a few additions for input validations. However, the above PR was using `six.assertCounEqual` for assertions which checks equality but not order. For paging predicate tests, it makes more sense to check ordering. - Client side codecs and holder classes for PagingPredicates and AnchorDataLists are added. - Some public methods, like `get_anchor`, `set_anchor`, `get_nearest_anchor_entry` is removed. `get_anchor` is defined on the public API on the Java side but I think it does not provide any functionality to the user.
This is the port of hazelcast#212 to the 4.0 branch. However, there are some differences from that PR. - Documentation of the feature is a little bit different since the client side sorting is removed. - Tests are more-or-less ported directly with a few additions for input validations. However, the above PR was using `six.assertCounEqual` for assertions which checks equality but not order. For paging predicate tests, it makes more sense to check ordering. - Client side codecs and holder classes for PagingPredicates and AnchorDataLists are added. - Some public methods, like `get_anchor`, `set_anchor`, `get_nearest_anchor_entry` is removed. `get_anchor` is defined on the public API on the Java side but I think it does not provide any functionality to the user.
* Implement PagingPredicate This is the port of #212 to the 4.0 branch. However, there are some differences from that PR. - Documentation of the feature is a little bit different since the client side sorting is removed. - Tests are more-or-less ported directly with a few additions for input validations. However, the above PR was using `six.assertCounEqual` for assertions which checks equality but not order. For paging predicate tests, it makes more sense to check ordering. - Client side codecs and holder classes for PagingPredicates and AnchorDataLists are added. - Some public methods, like `get_anchor`, `set_anchor`, `get_nearest_anchor_entry` is removed. `get_anchor` is defined on the public API on the Java side but I think it does not provide any functionality to the user. * address review comments
Support for Paging Predicate. Fixes issue #202