[SPARK-17861] Store data source partitions in metastore and push partition pruning into metastore

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Component/s: SQL
• Target Version/s: 2.1.0
• Assignee: Eric Liang
• Reporter: Reynold Xin
• Created: 11/Oct/16 00:57
• Updated: 01/Aug/18 18:11
• Resolved: 30/Nov/16 04:06

Description

Initially, Spark SQL does not store any partition information in the catalog for data source tables, because initially it was designed to work with arbitrary files. This, however, has a few issues for catalog tables:

1. Listing partitions for a large table (with millions of partitions) can be very slow during cold start.
2. Does not support heterogeneous partition naming schemes.
3. Cannot leverage pushing partition pruning into the metastore.

This ticket tracks the work required to push the tracking of partitions into the metastore. This change should be feature flagged.

Issue Links

• is depended upon by: HADOOP-13525 Optimize uses of FS operations in the ASF analysis frameworks and libraries
• is related to: SPARK-15691 Refactor and improve Hive support
• relates to: SPARK-16980 Load only catalog table partition metadata required to answer a query