-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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-23192] [SQL] Keep the Hint after Using Cached Data #20365
Conversation
LGTM |
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.
+1, LGTM.
Test build #86536 has finished for PR 20365 at commit
|
retest this please |
Test build #86544 has finished for PR 20365 at commit
|
Since the last change is just to change the test case name, I merge this PR. |
Thanks! Merged to master/2.3 |
## What changes were proposed in this pull request? The hint of the plan segment is lost, if the plan segment is replaced by the cached data. ```Scala val df1 = spark.createDataFrame(Seq((1, "4"), (2, "2"))).toDF("key", "value") val df2 = spark.createDataFrame(Seq((1, "1"), (2, "2"))).toDF("key", "value") df2.cache() val df3 = df1.join(broadcast(df2), Seq("key"), "inner") ``` This PR is to fix it. ## How was this patch tested? Added a test Author: gatorsmile <[email protected]> Closes #20365 from gatorsmile/fixBroadcastHintloss. (cherry picked from commit 613c290) Signed-off-by: gatorsmile <[email protected]>
Test build #86546 has finished for PR 20365 at commit
|
What changes were proposed in this pull request?
The hint of the plan segment is lost, when the plan segment is replaced by the cached data.
This PR is to fix it.
How was this patch tested?
Added a test