[
https://issues.apache.org/jira/browse/FLINK-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997003#comment-16997003
]
Danny Chen commented on FLINK-13197:
------------------------------------
[~dwysakowicz]
> And what about null handling? E.g. in hive 1.x all columns will be nullable,
> even if they are backed by
> literal.
For hive (or other external storage) views, we may need to add the projection
because it is hard to keep the nullability inference synced with Calcite.
If the view are create from Flink, the data type and nullability should always
expect to be correct.
We can add casts to fix only the nullability but not the field name.
BTW, if all the assumption is correct, we should not expect to have any plan
change with current code with the fix patch.
> Verify querying Hive's view in Flink
> ------------------------------------
>
> Key: FLINK-13197
> URL: https://issues.apache.org/jira/browse/FLINK-13197
> Project: Flink
> Issue Type: Test
> 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)
