[
https://issues.apache.org/jira/browse/SPARK-32018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179002#comment-17179002
]
Wenchen Fan edited comment on SPARK-32018 at 8/17/20, 2:05 PM:
---------------------------------------------------------------
The unsafe row bug fix has been reverted from 3.0/2.4, see the reason
https://github.com/apache/spark/pull/29450#issuecomment-674799489
was (Author: cloud_fan):
The unsafe row bug fix has been reverted from 3.0/2.4, see the reason
https://github.com/apache/spark/pull/29448#issuecomment-674723823
> Fix UnsafeRow set overflowed decimal
> ------------------------------------
>
> Key: SPARK-32018
> URL: https://issues.apache.org/jira/browse/SPARK-32018
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.4.6, 3.0.0
> Reporter: Allison Wang
> Assignee: Wenchen Fan
> Priority: Major
> Fix For: 3.1.0
>
>
> There is a bug that writing an overflowed decimal into UnsafeRow is fine but
> reading it out will throw ArithmeticException. This exception is thrown when
> calling {{getDecimal}} in UnsafeRow with input decimal's precision greater
> than the input precision. Setting the value of the overflowed decimal to null
> when writing into UnsafeRow should fix this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
