[
https://issues.apache.org/jira/browse/HIVE-23368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099930#comment-17099930
]
Jesus Camacho Rodriguez commented on HIVE-23368:
------------------------------------------------
Cool [~kgyrtkirk], you are right. I think this is a no issue then, and we can
ask users to explicitly create the MV correctly for the time being.
However, I think we should disable the bi rewrite then when we are creating a
MV or loading an MV into the registry, i.e., only trigger the new rules if
{{!getQB().isMaterializedView() && !ctx.isLoadingMaterializedView()}}.
Otherwise, for a exact match, we may end up rewriting to a MV that uses a
different algorithm to the one they selected in their config, which could
potentially lead to different error bound.
> MV rebuild should produce the same view as the one configured at creation time
> ------------------------------------------------------------------------------
>
> Key: HIVE-23368
> URL: https://issues.apache.org/jira/browse/HIVE-23368
> Project: Hive
> Issue Type: Sub-task
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
>
> There might be some configrations which might affect the rel-tree of the
> materialized views.
> In case rewrites to use datasketches for count(distinct) is enabled; the view
> should store sketches instead of distinct values
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
