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
Continue wait when using three filters with 10 values each #2748
Labels
Comments
hassankhan
added
backend:cube-store
Issues relating to Cube Store
backend:server
Issues relating to Cube Core's Server
bug
Something isn't working
labels
May 14, 2021
hassankhan
changed the title
Error in filters management
Continue wait when using more than two filters
May 14, 2021
hassankhan
changed the title
Continue wait when using more than two filters
Continue wait when using three filters with 10 values each
May 14, 2021
Hello @angelo-cavallo , Can you provide logs from Cube.js? Thanks |
There is an error in Cube Store inside |
ilya-biryukov
added a commit
that referenced
this issue
May 19, 2021
Caused by an error in handling of OR expressions. Also fix occasional incomplete partition filters on OR expressions.
ilya-biryukov
added a commit
that referenced
this issue
May 19, 2021
Caused by an error in handling of OR expressions. Also fix occasional incomplete partition filters on OR expressions.
ilya-biryukov
added a commit
that referenced
this issue
May 19, 2021
Caused by an error in handling of OR expressions. Also fix occasional incomplete partition filters on OR expressions.
Thanks for reporting this. Should be fixed when f6f0992 lands into the docker hub. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I add 3 or more filters to a query, each one with 10 values, It seems that cube can't return a result set (it keeps returning a "Continue wait" error). If I add only 2 filters, it works correctly no matter how many values I specify.
I'm using version 0.27.14 and I already built my pre-aggregations in Cube Store.
I've verified that all the query members are in the pre-aggregation, and that the granularities match on both the query and schema.
Source database: BigQuery
External database: Cube Store
The text was updated successfully, but these errors were encountered: