-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Regression in support of sort in queries [DATACASS-842] #1008
Labels
type: regression
A regression from a previous release
Milestone
Comments
Thanks for the report @lucboutier. That's caused by collecting sort orders in a |
mp911de
added a commit
that referenced
this issue
Jan 29, 2021
Replace stream() usage with for-loops where possible to reduce GC overhead. See #1008.
mp911de
added a commit
that referenced
this issue
Jan 29, 2021
We now apply sort-by properties individually on the built statement instead of collecting these into a Map first. Resolves #1008
mp911de
added a commit
that referenced
this issue
Jan 29, 2021
Replace stream() usage with for-loops where possible to reduce GC overhead. See #1008.
mp911de
added a commit
that referenced
this issue
Jan 29, 2021
We now apply sort-by properties individually on the built statement instead of collecting these into a Map first. Resolves #1008
That's fixed now. |
mp911de
added a commit
that referenced
this issue
Jan 29, 2021
Replace stream() usage with for-loops where possible to reduce GC overhead. See #1008.
Amazing! Thanks a lot for the great work! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Luc Boutier opened DATACASS-842 and commented
When migrating a project from cassandra 2.x to 3.x I encountered an issue in the ordering of sort parameters.
The clustering key of my object contains (in order) fields repairOrderId and revisionId and I was using the following query
val query = query(where("partitionKey").
is
(partitionKey)).sort(by(DESC, "repairOrderId", "revisionId"))return cassandraTemplate.selectOne(query, RepairOrderByBasket::class.java)
It seems that somehow the sort is mixing up and creates a statement with
that cassandra does not support (it requires the same order as clustering keys so
In my particular case it was actually just better to use a clustering ordering on the table definition rather than at the query level but I guess this can be an issue in some other context
No further details from DATACASS-842
The text was updated successfully, but these errors were encountered: