I have a dataset with an aggregation reflection on it. Unfortunately dremio doesn’t select it even it covers the executed query
SELECT APPROX_COUNT_DISTINCT(ProfileViews."Company ID") AS "usr_Count_of_Profile_Views_ok" FROM "@elshafey".common.profileViewsTest as "ProfileViews" GROUP BY ProfileViews."Profile View Context"
Reflection Definition: Aggregation Reflection Matched: 0, Chosen: 0, Match Latency: 0 ms Reflection Id: 177eb81c-c06d-4f9f-85d3-b8928efa6c69, Materialization Id: 3c265b06-f464-46dc-afd0-5145ad3e8ad0 Expiration: 3022-05-19T15:10:55Z Dataset: "@elshafey".common.profileViewsTest Age: 43 seconds Dimensions: Profile View Context, Measures: Profile View ID ( APPROX_COUNT_DISTINCT, COUNT, ) Company ID ( COUNT, APPROX_COUNT_DISTINCT, )
Matching Hints: Missing Field Employer ID Missing Field Job Seeker ID Missing Field Profile View Date Missing Field Current Approval Status Missing Field Job Seeker Signup Date
Why the planning consider those missing fields even they are not part of the query