[SPARK-20059] HbaseCredentialProvider uses wrong classloader

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0, 2.2.0
• Fix Version/s: 2.1.1, 2.2.0
• Component/s: Spark Core, YARN
• Assignee: Saisai Shao
• Reporter: Saisai Shao
• Created: 22/Mar/17 13:00
• Updated: 17/May/20 18:15
• Resolved: 29/Mar/17 17:10

Description

HBaseCredentialProvider uses system classloader instead of child classloader, which will make HBase jars specified with --jars fail to work, so here we should use the right class loader.

Besides in yarn cluster mode jars specified with --jars is not added into client's class path, which will make it fail to load HBase jars and issue tokens in our scenario. Also some customized credential provider cannot be registered into client.

So here I will fix this two issues.

Issue Links

• links to: [Github] Pull Request #17388 (jerryshao)