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
Regression after returning ResultSet instead of SortedQueryResultSet #11489
Labels
Milestone
Comments
@ahmetmircik Thanks for opening the issue here. I wasn't sure if it was an issue or just there is a new way to use the API. |
Set milestone to 3.9, will back-port to 3.8.x |
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Oct 10, 2017
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Oct 10, 2017
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Oct 10, 2017
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Oct 10, 2017
tombujok
pushed a commit
to tombujok/hazelcast
that referenced
this issue
Oct 10, 2017
tombujok
added a commit
that referenced
this issue
Oct 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
First see this group question.
Problem occurs in getSortedQueryResultSet method:
When returned object is SortedQueryResultSet there is no problem but when it is ResultSet failure happens.
The text was updated successfully, but these errors were encountered: