[HDFS-11689] New exception thrown by DFSClient#isHDFSEncryptionEnabled broke hacky hive code

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha4, 2.8.1
• Fix Version/s: 2.9.0, 3.0.0-alpha4, 2.8.2
• Assignee: Yongjun Zhang
• Reporter: Yongjun Zhang
• Created: 20/Apr/17 19:30
• Updated: 07/Jun/17 23:56
• Resolved: 21/Apr/17 21:28

Description

Though Hive should be fixed not to access DFSClient which is private to HADOOP, removing the throws added by HADOOP-14104 is a quicker solution to unblock hive.

Hive code

private boolean isEncryptionEnabled(DFSClient client, Configuration conf) {
  try {
    DFSClient.class.getMethod("isHDFSEncryptionEnabled");
  } catch (NoSuchMethodException e) {
    // the method is available since Hadoop-2.7.1
    // if we run with an older Hadoop, check this ourselves
    return !conf.getTrimmed(DFSConfigKeys.DFS_ENCRYPTION_KEY_PROVIDER_URI, "").isEmpty();
  }
  return client.isHDFSEncryptionEnabled();
}

Issue Links

• is broken by: HADOOP-14104 Client should always ask namenode for kms provider path.
• is related to: HDFS-11687 Add new public encryption APIs required by Hive
• is related to: HIVE-16490 Hive should not use private HDFS APIs for encryption