[SPARK-23521] SPIP: Standardize SQL logical plans with DataSourceV2

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Component/s: SQL
• Labels: SPIP
• Assignee: Unassigned
• Reporter: Ryan Blue
• Created: 27/Feb/18 01:48
• Updated: 22/Feb/23 23:17
• Resolved: 25/Sep/18 16:55

Description

Executive Summary: This SPIP is based on discussion about the DataSourceV2 implementation on the dev list. The proposal is to standardize the logical plans used for write operations to make the planner more maintainable and to make Spark's write behavior predictable and reliable. It proposes the following principles:

1. Use well-defined logical plan nodes for all high-level operations: insert, create, CTAS, overwrite table, etc.
2. Use planner rules that match on these high-level nodes, so that it isn’t necessary to create rules to match each eventual code path individually.
3. Clearly define Spark’s behavior for these logical plan nodes. Physical nodes should implement that behavior so that all code paths eventually make the same guarantees.
4. Specialize implementation when creating a physical plan, not logical plans. This will avoid behavior drift and ensure planner code is shared across physical implementations.

The SPIP doc presents a small but complete set of those high-level logical operations, most of which are already defined in SQL or implemented by some write path in Spark.

Issue Links

• is related to: SPARK-24251 DataSourceV2: Add AppendData logical operation
• is related to: SPARK-27066 SPIP: Identifiers for multi-catalog support
• is related to: SPARK-27067 SPIP: Catalog API for table metadata
• relates to: SPARK-22386 Data Source V2 improvements
• links to: SPIP Proposal: Standardize SQL logical plans with DataSourceV2
• links to: SPIP Vote Result: Adopted