cloud-fan commented on pull request #29026:
URL: https://github.com/apache/spark/pull/29026#issuecomment-705305987
There was an attempt to backport this fix but we decided not to as it breaks
backward compatibility. See
https://github.com/apache/spark/pull/29448#issuecomment-674723823
cloud-fan commented on pull request #29026:
URL: https://github.com/apache/spark/pull/29026#issuecomment-655336987
retest this please
This is an automated message from the Apache Git Service.
To respond to the message,
cloud-fan commented on pull request #29026:
URL: https://github.com/apache/spark/pull/29026#issuecomment-655294615
retest this please
This is an automated message from the Apache Git Service.
To respond to the message,
cloud-fan commented on pull request #29026:
URL: https://github.com/apache/spark/pull/29026#issuecomment-655259660
retest this please
This is an automated message from the Apache Git Service.
To respond to the message,
cloud-fan commented on pull request #29026:
URL: https://github.com/apache/spark/pull/29026#issuecomment-655259298
> So now we have UnsafeRow.setDecimal silently returns a null for an
overflowed decimal value in setDecimal, but getDecimal throws error. There is
inconsistency here. Why is
cloud-fan commented on pull request #29026:
URL: https://github.com/apache/spark/pull/29026#issuecomment-654979274
cc @skambha @rednaxelafx @viirya
This is an automated message from the Apache Git Service.
To respond to the
