GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/7978
[SPARK-9644] [SQL] Support update DecimalType with precision > 18 in
UnsafeRow
In order to support update a varlength (actually fixed length) object, the
space should be preserved even it's null. And, we can't call setNullAt(i) for
it anymore, we because setNullAt(i) will remove the offset of the preserved
space, should call setDecimal(i, null, precision) instead.
After this, we can do hash based aggregation on DecimalType with precision
> 18. In a tests, this could decrease the end-to-end run time of aggregation
query from 37 seconds (sort based) to 24 seconds (hash based).
cc @rxin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davies/spark update_decimal
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/7978.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #7978
----
commit 10d0964879919770d2d153ee989b2e941e4f29ca
Author: Davies Liu <[email protected]>
Date: 2015-08-05T23:55:27Z
support set decimal with precision > 18
----
---
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]
