Github user yucai commented on the pull request:
https://github.com/apache/spark/pull/13204#issuecomment-222431501
Dear Davies,
Sometimes, it could be hard for me to recognize the boundary of whole stage
codegen,
for example, in below SMJ, there are 3 separate whole stage codegen
actually, can we read this info from the physical plan output?
```
+- Exchange hashpartitioning(sourceIP#0, 200), None
+- *TungstenAggregate(key=[sourceIP#0], ......
+- *Project [pagerank#30,sourceIP#0,adRevenue#3]
+- *SortMergeJoin [pageURL#29], [destURL#1], Inner, None
:- *Sort [pageURL#29 ASC], false, 0
: +- Exchange hashpartitioning(pageURL#29, 200), None
: +- ......
+- *Sort [destURL#1 ASC], false, 0
+- Exchange hashpartitioning(destURL#1, 200), None
+- ......
```
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]