[
https://issues.apache.org/jira/browse/FLINK-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989288#comment-16989288
]
Danny Chen commented on FLINK-13197:
------------------------------------
Thanks [~dwysakowicz] and [~lirui] for reporting this ~
I thought a lot, and think we still should not add redundant casts/AS operators
above the view relational expression.
- For column alias, i'm thinking about to support view alias from the create
view statement, which should be finished in FLIP-71
- For nullability, we should fix it from the type inference
I'm always agains with the redundant nodes because it add a useless projection
above the view thus would change the logical plan (make it more complicated and
we may lose some plan promotion like project merge or transpose or reduction).
> 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)
