You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have a measure that uses a dimension with sub_query and propagate_filters_to_sub_query set to true. When creating a pre-aggregation in the same cube and querying the measure, it errors out with the following error message
RequestError: Error: Internal: Error during planning: Table or CTE with name '<table name>' not found
To Reproduce
I used the following schema to create the cube
This error out with the message given above.
I think this is happening because, Cube is detecting that it can be satisfied via the pre-aggregation and thus runs query on pre-aggregation only. This causes the sub-query to fail.
Expected behavior
Cube should detect the sub-query and not run this specific query on pre-aggregations but use the source database.
Version:
0.36.1
Additional Comments
One workaround is to create two different cubes one with the pre-aggregation and one without it and add the measure with sub-query to the one without pre-aggregation. If there's a better workaround, please let me know.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a measure that uses a dimension with
sub_query
andpropagate_filters_to_sub_query
set totrue
. When creating a pre-aggregation in the same cube and querying the measure, it errors out with the following error messageTo Reproduce
I used the following schema to create the cube
I am then running the following query
This error out with the message given above.
I think this is happening because, Cube is detecting that it can be satisfied via the pre-aggregation and thus runs query on pre-aggregation only. This causes the sub-query to fail.
Expected behavior
Cube should detect the sub-query and not run this specific query on pre-aggregations but use the source database.
Version:
0.36.1
Additional Comments
The text was updated successfully, but these errors were encountered: