Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7408#issuecomment-121484810
I came up with a workaround which allows GeneratedOrdering to be used as
the ordering when computing bounds in the RangePartitioner. Using a generated
ordering might not be a huge win here, so I'd be okay with backing out of this
change if someone thinks I should.
---
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]
