[
https://issues.apache.org/jira/browse/HIVE-18163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270276#comment-16270276
]
Zoltan Haindrich commented on HIVE-18163:
-----------------------------------------
[~jcamachorodriguez]: I understand your concern; and I think it would be
possible - I've choosen this direction because it was the smallest fix
To constrain the view update of the cache to happen during its own call ; but
after the statstask, I see the following options:
* somehow add some "afterexecute" callback to the driver
* add a task to register/unregister items from/to materializedview cache
* add a set of "if"-s in the ddltask/statstask to enable the materializedview
cache to see the updated table entry.
I'll keep thinking about further alternatives; and implement the one which
looks the most promising; if you have other ideas, just throw them in :)
> Stats: create materialized view should also collect stats
> ---------------------------------------------------------
>
> Key: HIVE-18163
> URL: https://issues.apache.org/jira/browse/HIVE-18163
> Project: Hive
> Issue Type: Sub-task
> Components: Statistics
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Attachments: HIVE-18163.01.patch
>
>
> not having basic stats on the materialized view may cause it to be "ruled
> out" as a viable alternative by the cbo.
> repro set {{set hive.stats.deserialization.factor=10.0}} in
> {{ql/src/test/queries/clientpositive/materialized_view_create_rewrite.q}}
> blocks: HIVE-18149
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
