Most of our GroupBy queries are very fast, completing in less than one second.
One of our dimensions may have a very high cardinality (100k+ values).
If I include that dimension in a groupBy query, it could spend 30+ seconds and then fail with a “Resource limit exceeded” error.
Is there a way to make it fail faster, so I can warn the user that they must add more filtering to the query, so fewer groups would be returned?
I tried reducing maxMergingDictionarySize to 1000, but the query still spent 30+ seconds before failing.
Similarly, setting limit:1 in the limitSpec did not help.
Thanks for any ideas.