Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9646#issuecomment-156225043
This seems fine for now, but its not clear to me why the right answer isn't
to read it in as a higher precision signed type.
---
If your project is set up for it, you
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9646#issuecomment-156225166
Merging to master and 1.6
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9646
---
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
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9646#issuecomment-156322187
@marmbrus That's also an option, but seems somewhat confusing to me.
Especially, in this way `UINT_64` has to be mapped to a fractional type.
Besides, I just checked
