Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43038225
Hey @kanzhang, while this is a partial fix for one case, it's not going to
solve SPARK-1817 in general. The right thing to do will be to warn or throw a
better error when partitions are discovered to have different sizes. I'd
suggest opening a separate JIRA for updating NumericRange (the change here) and
keeping 1817 open.
---
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.
---
