Open Betilopeza opened 2 months ago
@Betilopeza It seems distinctUuid
is a measure however you're using it in GROUP BY
. I expect to see it inside COUNT(DISTINCT distinctUuid)
aggregation reference. Could you please elaborate on your use case?
Hello, yes we tried in the group by, because in the measure sections the preaggregation was not working either! I send you the screenshots. Preaggregation:
@Betilopeza There're dimensions in this pre-aggregation and this pre-aggregation is non-additive. So it couldn't match a query without dimensions defined. Please see https://cube.dev/docs/product/caching/matching-pre-aggregations.
We are trying to make work this preaggregation: Preaggregation:
As you can see it actually doesn´t have any dimension, so it´s happenning what I send you in the previous message. In playground works perfectly, but not in metabase. I did't get why you said that we have dimensions
@Betilopeza Unfortunately we can't reproduce it on our side. If you're in Cube Cloud please prepare a branch with a description on how to reproduce and file a ticket with the support team. We'll take a look.
Thanks! Unfortunately, we haven't been able to reach support since February, so I don't think that would be an option.
Hi @Betilopeza, you can send the link to your branch with a reproduction and any relevant information to me via igor@cube.dev.
Hello! we are testing preaggregations to improve the latency for the questions to appear in Metabase dashboards. We are currently using:
For some reason, when we create a preaggregation with measures that worked perfectly fine in our playground, but when queried from Metabase, are not preaggregated as shown below in the example.
The dynamic schema for that table is this one:
And this is our cube.js
Please if you can check if we are doing something wrong, or if we are missing something, would be really helpful