-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ORDER BY is not working for preaggregations queries #8255
Comments
Hi @b-jan 👋 Sorry, I wasn't able to reproduce this. By any chance, can you provide more details? would love to see a screenshot of your Playground where this order-less SQL can be seen—together with the order settings. Also, if you can reproduce this in Cube Cloud (you can create a free account), it would be tremendously helpful.
This is a limitation of how JSON is parsed in web browsers. If your measures have their values over a certain number ( |
Thanks a lot for the answer @igorlukanin. Still even with this option, I still have the order issue. |
This is very helpful, thank you! Let me tag @paveltiunov and @ovr in case they can guess what's going on (wrong) here. Does this reproduce if you change your cube definitions' |
Describe the bug
Using BigQuery and matching a preaggregation, a query with
order
parameter on ameasure
returns unsorted results.The generated SQL query that I can inspect in the playground does not use any ORDER BY clause.
Example of a query:
The generated SQL is:
Expected behavior
order should be working when a preaggregation is matched.
Version:
"@cubejs-backend/bigquery-driver": "0.35.30",
"@cubejs-backend/server": "0.35.30"
Other question:
Also I noticed the count measure is returned by preaggregations (from BigQuery) as a string instead of a number.
Is there any reason for this to happen?
The text was updated successfully, but these errors were encountered: