After migration to 3.1.1, I’m unfortunately running into the case when an aggregation reflection is not used
I have two aggregation reflections on a parquet source dataset (one with few columns, one with more columns), and when I basically test the simple one (called basic), the reflection is not used with message “Considered : not matched”
Any insight why it is not chosen ?
Here is the query profile :1af618b8-f20a-484e-96f1-279eb96a9e09.zip (23.8 KB)
The definition os the reflection is as follow, and I simply try to do
EXPLAIN PLAN FOR SELECT wtbid,action, sum(prc)
group by wtbid,action
Reflection Definition: basic
Matched: 0, Chosen: 0, Match Latency: 0 ms
Reflection Id: 02d67809-bbc9-452e-9c1b-d8884a3b7238, Materialization Id: a1418aa7-c1ae-4073-9c62-2aa9c5fd71b0
Age: 4 hours 57 minutes 17 seconds
Dimensions: distri_id, is_preview, auto, is_bot_traffic, module, is_bot, ts, wtbid, is_mobile, action, type, fmt, dir0, dir1, dir2, dir3, is_pc,
- prc ( SUM, COUNT, )
I didn’t have this issue with 3.0 release.