-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-33427][SQL][FOLLOWUP] Put key and value into IdentityHashMap sequantially #30459
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
Conversation
| proxyExpressionCurrentId += 1 | ||
|
|
||
| proxyMap.putAll(e.map(_ -> proxy).toMap.asJava) | ||
| e.map(proxyMap.put(_, proxy)) |
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.
cc @cloud-fan
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #131507 has finished for PR 30459 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Thanks @HyukjinKwon |
...lyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/SubExprEvaluationRuntime.scala
Show resolved
Hide resolved
|
Let me merge this in. The last is comment-only. |
|
Merged to master. |
|
Test build #131525 has finished for PR 30459 at commit
|
|
Test build #131516 has finished for PR 30459 at commit
|
|
late LGTM |
|
Thanks @maropu |
What changes were proposed in this pull request?
This follow-up fixes an issue when inserting key/value pairs into
IdentityHashMapinSubExprEvaluationRuntime.Why are the changes needed?
The last commits to #30341 follows review comment to use
IdentityHashMap. Because we leverageIdentityHashMapto compare keys in reference, we should not convert expression pairs to Scala map before inserting. Scala map compares keys by equality so we will loss keys with different references.Does this PR introduce any user-facing change?
No
How was this patch tested?
Run benchmark to verify.