Backward compatibility of CDH 5.16 from CDH 6.1 client

[#1]

Our Application previously using CDH 5.8 jars in client side. Now we have been upgrading to CDH 6.1, so we have modified the relevant jars to new CDH 6.1 jars.
i.e, hadoop-auth-3.0.0-cdh6.1.1.jar,hadoop-common-3.0.0-cdh6.1.1.jar,hive-exec-2.1.1-cdh6.1.1.jar,hive-jdbc-2.1.1-cdh6.1.1.jar,hive-metastore-2.1.1-cdh6.1.1.jar,hive-service-2.1.1-cdh6.1.1.jar,httpclient-4.5.3.jarhttpcore-4.4.6.jar

After upgrading jars to CDH 6.1 in client side, when we connect to CDH 5.16 or 5.13 hive jdbc , we are getting the following exception.


"java.lang.Exception: Could not open client transport with JDBC Uri: jdbc:hive2://localhost:10000/default;user=hdfs;password=********:
Could not establish connection to jdbc:hive2://localhost:10000/default;user=hdfs;password=********:

Required field 'client_protocol' is unset! Struct:TOpenSessionReq(client_protocol:null, configuration:{use:database=default})"


Is CDH 6.1 jars supports backward compatibility ?

[#2]

Cloudera CDH provides backwards compatibility within minor release upgrades (5.x to 5.y, or 6.x to 6.y, etc.).

The major release upgrades (5.x to 6.x) carry a very large amount of differences between them and do not guarantee backwards compatibility.

Please see our upgrade impact assessment docs for more: https://www.cloudera.com/documentation/enterprise/upgrade/topics/ug_overview.html#concept_ch1_xw1_yw

You'll need to use a 6.x client with a 6.x server. For JDBC connectors compatible with 6.x, see https://www.cloudera.com/downloads/connectors/hive/jdbc/2-6-2.html