-
Notifications
You must be signed in to change notification settings - Fork 29.3k
[SPARK-31866][SQL][DOCS] Add COALESCE/REPARTITION/REPARTITION_BY_RANGE Hints to SQL Reference #28672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-31866][SQL][DOCS] Add COALESCE/REPARTITION/REPARTITION_BY_RANGE Hints to SQL Reference #28672
Changes from 2 commits
0b3e765
60fdb93
8a7fa09
7f97fe3
bc4fdfc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| --- | ||
| layout: global | ||
| title: Join Hints | ||
| displayTitle: Join Hints | ||
| title: Hints | ||
| displayTitle: Hints | ||
| license: | | ||
| Licensed to the Apache Software Foundation (ASF) under one or more | ||
| contributor license agreements. See the NOTICE file distributed with | ||
|
|
@@ -21,14 +21,69 @@ license: | | |
|
|
||
| ### Description | ||
|
|
||
| Join Hints allow users to suggest the join strategy that Spark should use. Prior to Spark 3.0, only the `BROADCAST` Join Hint was supported. `MERGE`, `SHUFFLE_HASH` and `SHUFFLE_REPLICATE_NL` Joint Hints support was added in 3.0. When different join strategy hints are specified on both sides of a join, Spark prioritizes hints in the following order: `BROADCAST` over `MERGE` over `SHUFFLE_HASH` over `SHUFFLE_REPLICATE_NL`. When both sides are specified with the `BROADCAST` hint or the `SHUFFLE_HASH` hint, Spark will pick the build side based on the join type and the sizes of the relations. Since a given strategy may not support all join types, Spark is not guaranteed to use the join strategy suggested by the hint. | ||
| Hints give users a way to suggest how Spark SQL to use specific approaches to generate its execution plan. | ||
|
|
||
| ### Syntax | ||
|
|
||
| ```sql | ||
| /*+ join_hint [ , ... ] */ | ||
| /*+ hint [ , ... ] */ | ||
| ``` | ||
|
|
||
| ### Partitioning Hints | ||
|
|
||
| `COALESCE`/`REPARTITION`/`REPARTITION_BY_RANGE` hints have functionalities equivalent to those of the | ||
| `Dataset` `coalesce`/`repartition`/`repartitionByRange` APIs. The `COALESCE` hint can be used to reduce | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about moving the explanations for each hint (e.g., |
||
| the number of partitions to the specified number of partitions. The `REPARTITION`/`REPARTITION_BY_RANGE` | ||
| hint can be used to repartition to the specified number of partitions using the specified partitioning expressions. | ||
| The `COALESCE` hint takes a partition number as a | ||
| parameter. The `REPARTITION` hint takes a partition number, column names, or both as parameters. | ||
| The `REPARTITION_BY_RANGE` hint takes column names and an optional partition number as parameters. | ||
| These hints give users a way to tune performance and control the number of output files in Spark SQL. | ||
|
|
||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: remove the unencessary blank line. |
||
| ### Examples | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ditto, #### Examples |
||
| ```sql | ||
| SELECT /*+ COALESCE(3) */ * FROM t; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about showing a spark plan via |
||
|
|
||
| EXPLAIN SELECT /*+ COALESCE(3) */ * FROM t; | ||
| == Physical Plan == | ||
| Coalesce 3 | ||
| +- *(1) ColumnarToRow | ||
| +- FileScan parquet default.t[name#5,c#6] Batched: true, DataFilters: [], Format: Parquet, | ||
| Location: CatalogFileIndex[file:/spark/spark-warehouse/t], PartitionFilters: [], | ||
| PushedFilters: [], ReadSchema: struct<name:string> | ||
|
|
||
| SELECT /*+ REPARTITION(3) */ * FROM t; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We still need these statements having no output as the example?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One more comment; probably, the join hint section should have the same format for the examples.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think I will only have one example for explain. Otherwise the example section will be too long. |
||
|
|
||
| SELECT /*+ REPARTITION(c) */ * FROM t; | ||
|
|
||
| SELECT /*+ REPARTITION(3, c) */ * FROM t; | ||
|
|
||
| EXPLAIN SELECT /*+ REPARTITION(3, c) */ * FROM t; | ||
| == Physical Plan == | ||
| Exchange hashpartitioning(c#6, 3), false, [id=#148] | ||
| +- *(1) ColumnarToRow | ||
| +- FileScan parquet default.t[name#5,c#6] Batched: true, DataFilters: [], Format: Parquet, | ||
| Location: CatalogFileIndex[file:/spark/spark-warehouse/t], PartitionFilters: [], | ||
| PushedFilters: [], ReadSchema: struct<name:string> | ||
|
|
||
| SELECT /*+ REPARTITION_BY_RANGE(c) */ * FROM t; | ||
|
|
||
| SELECT /*+ REPARTITION_BY_RANGE(3, c) */ * FROM t; | ||
|
|
||
| EXPLAIN SELECT /*+ REPARTITION_BY_RANGE(3, c) */ * FROM t; | ||
| == Physical Plan == | ||
| Exchange rangepartitioning(c#6 ASC NULLS FIRST, 3), false, [id=#167] | ||
| +- *(1) ColumnarToRow | ||
| +- FileScan parquet default.t[name#5,c#6] Batched: true, DataFilters: [], Format: Parquet, | ||
| Location: CatalogFileIndex[file:/spark/spark-warehouse/t], PartitionFilters: [], | ||
| PushedFilters: [], ReadSchema: struct<name:string> | ||
| ``` | ||
|
|
||
|
|
||
| ### Join Hints | ||
|
|
||
| Join Hints allow users to suggest the join strategy that Spark should use. Prior to Spark 3.0, only the `BROADCAST` Join Hint was supported. `MERGE`, `SHUFFLE_HASH` and `SHUFFLE_REPLICATE_NL` Joint Hints support was added in 3.0. When different join strategy hints are specified on both sides of a join, Spark prioritizes hints in the following order: `BROADCAST` over `MERGE` over `SHUFFLE_HASH` over `SHUFFLE_REPLICATE_NL`. When both sides are specified with the `BROADCAST` hint or the `SHUFFLE_HASH` hint, Spark will pick the build side based on the join type and the sizes of the relations. Since a given strategy may not support all join types, Spark is not guaranteed to use the join strategy suggested by the hint. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
|
|
||
| ### Join Hints Types | ||
|
|
||
| * **BROADCAST** | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about rephrasing it like this?
Partitioning hints allow users to suggest a partitioning way that Spark should follow.
COALESCE,REPARTITION, andREPARTITION_BY_RANGEhints are supported and they are equivalent tocoalesce,repartition, andrepartitionByRangeDataset APIs, respectively.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, could you add links to the Dataset APIs if we describe them here? https://spark.apache.org/docs/latest/api/scala/index.html#org.apache.spark.sql.Dataset