[ 
https://issues.apache.org/jira/browse/FLINK-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581257#comment-17581257
 ] 

luoyuxia commented on FLINK-19957:
----------------------------------

Although the question is asked one year ago. But still put answer in here in 
case some others need it.

The hive-exec 2.0 bundled in flink-sql-connector-hive-2.2.0 is not expected to 
support Hadoop3, so the exception is thrown. 

When you upgrade flink-sql-connector-hive-2.3.6, there won't be any validation 
exception as the hive-exec 
2.3.x[HIVE-16081|https://issues.apache.org/jira/browse/HIVE-16081] bundled 
support Hadoop3. But since the Hive cluster isn't hive-2.3.x, use a higher 
version client will cause other excpetion.

> 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: Not a Priority
>              Labels: auto-deprioritized-critical, auto-deprioritized-major, 
> auto-deprioritized-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