GitHub user carsonwang opened a pull request:
https://github.com/apache/spark/pull/16952
[SPARK-19620][SQL]Fix incorrect exchange coordinator id in the physical plan
## What changes were proposed in this pull request?
When adaptive execution is enabled, an exchange coordinator is used in the
Exchange operators. For Join, the same exchange coordinator is used for its two
Exchanges. But the physical plan shows two different coordinator Ids which is
confusing.
This PR is to fix the incorrect exchange coordinator id in the physical
plan. The coordinator object instead of the `Option[ExchangeCoordinator]`
should be used to generate the identity hash code of the same coordinator.
## How was this patch tested?
manual tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/carsonwang/spark FixCoordinatorId
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16952.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #16952
----
commit b2eb68afee9673274122f241f5d9eb64142a509f
Author: Carson Wang <carson.w...@intel.com>
Date: 2017-02-16T06:22:45Z
Fix incorrect exchange coordinator id
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
