[SPARK-11783] When deployed against remote Hive metastore, HiveContext.executionHive points to wrong metastore

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.5.1, 1.6.0
• Fix Version/s: 1.6.0
• Component/s: SQL
• Target Version/s: 1.5.3, 1.6.0
• Assignee: Cheng Lian
• Reporter: Cheng Lian
• Created: 17/Nov/15 17:35
• Updated: 03/Apr/17 15:12
• Resolved: 24/Nov/15 23:09

Description

When using remote metastore, execution Hive client somehow is initialized to point to the actual remote metastore instead of the dummy local Derby metastore.

To reproduce this issue:

1. Configuring conf/hive-site.xml to point to a remote Hive 1.2.1 metastore.
2. Set hive.metastore.uris to thrift://localhost:9083.
3. Start metastore service using $HIVE_HOME/bin/hive --service metastore
4. Start Thrift server with remote debugging options
5. Attach the debugger to the Thrift server driver process, we can verify that executionHive points to the remote metastore rather than the local execution Derby metastore.

Issue Links

• blocks: SPARK-11785 When deployed against remote Hive metastore with lower versions, JDBC metadata calls throws exception
• relates to: SPARK-9686 Spark Thrift server doesn't return correct JDBC metadata
• links to: [Github] Pull Request #9895 (liancheng)