[ 
https://issues.apache.org/jira/browse/FLINK-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-19957:
-----------------------------------
    Labels: auto-deprioritized-critical auto-deprioritized-major stale-minor  
(was: auto-deprioritized-critical auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> flink-sql-connector-hive incompatible with cdh6
> -----------------------------------------------
>
>                 Key: FLINK-19957
>                 URL: https://issues.apache.org/jira/browse/FLINK-19957
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Hive
>    Affects Versions: 1.11.2
>         Environment: Flink 1.11.2
> Hadoop 3.0.0-cdh6.3.1
> Hive 2.1.1-cdh6.3.1
>            Reporter: Cheng Pan
>            Priority: Minor
>              Labels: auto-deprioritized-critical, auto-deprioritized-major, 
> stale-minor
>
> According to Flink docs, we should use flink-sql-connector-hive-2.2.0(which 
> should compatible with hive 2.0.0 - 2.2.0), actually, we got a exception: 
> Unrecognized Hadoop major version number: 3.0.0-cdh6.3.1;
> If use flink-sql-connector-hive-2.3.6 (which should compatible with 2.3.0 - 
> 2.3.6), encounter another exception: org.apache.thrift.TApplicationException: 
> Invalid method name: 'get_table_req'
> If copy flink-connector-hive_2.11-1.11.2.jar and hive-exec-2.1.1-cdh6.3.1.jar 
> to flink/lib, not work again. Caused by: java.lang.ClassNotFoundException: 
> com.facebook.fb303.FacebookService$Iface



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to