[
https://issues.apache.org/jira/browse/HIVE-11762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dere updated HIVE-11762:
------------------------------
Attachment: HIVE-11762.3.patch
We're probably missing a dependency somewhere during the Spark tests, if anyone
has any ideas please chime in.
I've changed the patch so that the new changes only happen within
setKeyProvider() (which should only happen during tests requiring encryption),
as opposed to doing those reflection methods during static initialization. I'm
hoping this minimizes the risk of a Hadoop23Shims failure due to this class not
found issue.
> TestHCatLoaderEncryption failures when using Hadoop 2.7
> -------------------------------------------------------
>
> Key: HIVE-11762
> URL: https://issues.apache.org/jira/browse/HIVE-11762
> Project: Hive
> Issue Type: Bug
> Components: Shims, Tests
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: HIVE-11762.1.patch, HIVE-11762.2.patch,
> HIVE-11762.3.patch
>
>
> When running TestHCatLoaderEncryption with -Dhadoop23.version=2.7.0, we get
> the following error during setup():
> {noformat}
> testReadDataFromEncryptedHiveTableByPig[5](org.apache.hive.hcatalog.pig.TestHCatLoaderEncryption)
> Time elapsed: 3.648 sec <<< ERROR!
> java.lang.NoSuchMethodError:
> org.apache.hadoop.hdfs.DFSClient.setKeyProvider(Lorg/apache/hadoop/crypto/key/KeyProviderCryptoExtension;)V
> at
> org.apache.hadoop.hive.shims.Hadoop23Shims.getMiniDfs(Hadoop23Shims.java:534)
> at
> org.apache.hive.hcatalog.pig.TestHCatLoaderEncryption.initEncryptionShim(TestHCatLoaderEncryption.java:252)
> at
> org.apache.hive.hcatalog.pig.TestHCatLoaderEncryption.setup(TestHCatLoaderEncryption.java:200)
> {noformat}
> It looks like between Hadoop 2.6 and Hadoop 2.7, the argument to
> DFSClient.setKeyProvider() changed:
> {noformat}
> @VisibleForTesting
> - public void setKeyProvider(KeyProviderCryptoExtension provider) {
> - this.provider = provider;
> + public void setKeyProvider(KeyProvider provider) {
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
