[
https://issues.apache.org/jira/browse/FLINK-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz closed FLINK-13197.
------------------------------------
Resolution: Fixed
Fixed in:
master: 4e4dcf521748538aa164124fd613c9fe096ea604
1.10: 3d70c75477705b71acc83c010e7b89fce6c78c19
> Fix Hive view row type mismatch when expanding in planner
> ---------------------------------------------------------
>
> Key: FLINK-13197
> URL: https://issues.apache.org/jira/browse/FLINK-13197
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Hive, Table SQL / Planner
> 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)
