[
https://issues.apache.org/jira/browse/FLINK-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989334#comment-16989334
]
Rui Li commented on FLINK-13197:
--------------------------------
[~dwysakowicz] [~danny0405] Thanks for your inputs. I'm not very familiar with
the Calcite logics here, but just curious why we even care about the row type
returned by the catalog? A view is essentially just a query, and the row type
from the the catalog is what the external system "thinks" this query will
produce. I don't think we consult external system for result types of ordinary
queries. So why do we do that for views?
> support querying Hive's view in Flink
> -------------------------------------
>
> Key: FLINK-13197
> URL: https://issues.apache.org/jira/browse/FLINK-13197
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Hive
> Reporter: Bowen Li
> Assignee: Rui Li
> Priority: Major
> Fix For: 1.10.0
>
>
> One goal of HiveCatalog and hive integration is to enable Flink-Hive
> interoperability, that is Flink should understand existing Hive meta-objects,
> and Hive meta-objects created thru Flink should be understood by Hive.
> Taking an example of a Hive view v1 in HiveCatalog and database hc.db. Unlike
> an equivalent Flink view whose full path in expanded query should be
> hc.db.v1, the Hive view's full path in the expanded query should be db.v1
> such that Hive can understand it, no matter it's created by Hive or Flink.
> [~lirui] can you help to ensure that Flink can also query Hive's view in both
> Flink planner and Blink planner?
> cc [~xuefuz]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
