The easy answer to this is that SortMergeJoin ensure an outputOrdering, while BroadcastHashJoin doesn't, ie. after running a BroadcastHashJoin you don't know which is going to be the order of the output since nothing enforces it.
Hope this helps. Thanks. Marco 2018-06-28 15:46 GMT+02:00 吴晓菊 <chrysan...@gmail.com>: > > We see SortMergeJoinExec is implemented with outputPartitioning&outputOrdering > while BroadcastHashJoinExec is only implemented with outputPartitioning. > Why is the design? > > Chrysan Wu > Phone：+86 17717640807 > >
