andygrove opened a new issue, #1967:
URL: https://github.com/apache/datafusion-ballista/issues/1967
**Is your feature request related to a problem or challenge? Please describe
what you are trying to do.**
When viewing distributed plans, it isn't obvious which input stages would be
read by `UnresolvedShuffleExec`:
```
=== Stage 5 ===
SortShuffleWriterExec: partitioning=Hash([o_orderkey@7], 16)
ProjectionExec: expr=[c_custkey@0 as c_custkey, c_name@1 as c_name,
c_address@2 as c_address, c_nationkey@3 as c_nationkey, c_phone@4 as c_phone,
c_acctbal@5 as c_acctbal, c_comment@6 as c_comment, o_orderkey@7 as o_orderkey]
SortMergeJoinExec: join_type=Inner, on=[(c_custkey@0, o_custkey@1)]
SortExec: expr=[c_custkey@0 ASC], preserve_partitioning=[true]
UnresolvedShuffleExec: partitioning: Hash([c_custkey@0], 16)
SortExec: expr=[o_custkey@1 ASC], preserve_partitioning=[true]
UnresolvedShuffleExec: partitioning: Hash([o_custkey@1], 16)
```
**Describe the solution you'd like**
I think it would be better to include the stage id e.g.
`UnresolvedShuffleExec: stage=3`.
**Describe alternatives you've considered**
**Additional context**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
