Github user caneGuy commented on the issue:
https://github.com/apache/spark/pull/19764
Firstly , thanks too much @hvanhovell .
And sorry for replying so late since i have some other things to handle
during these time.
For the question, i think the ordering will not be broken.I did not modify
the 'RangePartitioner' itself.But optimize the partitioner strategy passed from
sql.And this will not break the 'Partitioner' contract since the same key will
still map to the same partition.
Notice that key here contains attribute added by second order.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
