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
Typically the dimension columns are used in filter and group by. However, technically nothing prevents user from doing a filter on a non-dimension column. So, we need to update the query inverted index and sorted index recommender (QueryInvertedSortedIndexRecommender) and remove this limitation. This will allow rule engine to recommend inverted or sorted index on non-dimension columns as well
This issue is followup for issue #6937
The text was updated successfully, but these errors were encountered:
GSharayu
changed the title
Changes in inverted index rule engine to handle DateTime column
Changes in query inverted and sorted index rule engine recommender to handle non-dimension columns
Jun 4, 2021
GSharayu
changed the title
Changes in query inverted and sorted index rule engine recommender to handle non-dimension columns
Changes in QueryInvertedSortedIndexRecommender to handle non-dimension columns
Jun 4, 2021
GSharayu
added a commit
to GSharayu/pinot
that referenced
this issue
Jun 9, 2021
Typically the dimension columns are used in filter and group by. However, technically nothing prevents user from doing a filter on a non-dimension column. So, we need to update the query inverted index and sorted index recommender (QueryInvertedSortedIndexRecommender) and remove this limitation. This will allow rule engine to recommend inverted or sorted index on non-dimension columns as well
This issue is followup for issue #6937
The text was updated successfully, but these errors were encountered: