[
https://issues.apache.org/jira/browse/HIVE-14496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637728#comment-15637728
]
Jesus Camacho Rodriguez commented on HIVE-14496:
------------------------------------------------
- About the separated table in the metastore, I understand what you mean. Will
we retrieve 'always' the information about the views when we query the
metastore in getTable()? I thought we did not, but I think I was confused and
we do. I will revert it then; maybe in the future, if we continue adding view
specific columns, we can take it back.
- I added the creation time when I thought more than one HS2 instance would be
able to edit the table information in the metastore. As we talked offline, this
should not be the case, thus it should be fine and I will remove it. Btw, if I
remember correctly, the time was just taken from metastore information, it is
not something that I was creating myself, thus in this case it should be robust.
- I will extend the rule to match Proj-FIL. About TS-Proj, it would not make
much sense in this context, since there is not much gain scanning the view
instead of the table, right? (unless you take into account properties of the
view such as sorting or partitioning, which we do not right now).
- If I remember correctly, I load all the views for the current user. The
problem is that I cannot add views for other users, since I do not have
permissions to do so, e.g. if we are using any kind of authentication. All
metastore methods seem to check current user permissions. Or is there any way
to bypass the authentication to the metastore to retrieve all tables (I thought
that was not allowed, since otherwise anybody could bypass that security
measures)?
- That's done on the Calcite side by the rewriting engine, although we could
add further filtering in the rule itself (in fact, currently early filtering is
only table based, we have not implemented anything more sophisticated yet).
> Enable Calcite rewriting with materialized views
> ------------------------------------------------
>
> Key: HIVE-14496
> URL: https://issues.apache.org/jira/browse/HIVE-14496
> Project: Hive
> Issue Type: Sub-task
> Components: Materialized views
> Affects Versions: 2.2.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-14496.01.patch, HIVE-14496.02.patch,
> HIVE-14496.patch
>
>
> Calcite already supports query rewriting using materialized views. We will
> use it to support this feature in Hive.
> In order to do that, we need to register the existing materialized views with
> Calcite view service and enable the materialized views rewriting rules.
> We should include a HiveConf flag to completely disable query rewriting using
> materialized views if necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
