You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/06/24 16:10:00 UTC
[jira] [Commented] (ARROW-16600) [Java] Enable configurable scale coercion of BigDecimal
[ https://issues.apache.org/jira/browse/ARROW-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558559#comment-17558559 ]
Todd Farmer commented on ARROW-16600:
-------------------------------------
[~jswenson] : I've put up a [PR adding configurable handling of BigDecimals|https://github.com/apache/arrow/pull/13433] with mismatched scale. If you have comments on how this solves (or fails to solve) your use case, please feel free to comment.
> [Java] Enable configurable scale coercion of BigDecimal
> -------------------------------------------------------
>
> Key: ARROW-16600
> URL: https://issues.apache.org/jira/browse/ARROW-16600
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Java
> Affects Versions: 8.0.0
> Reporter: Todd Farmer
> Assignee: Todd Farmer
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Per ARROW-16427, JDBC drivers sometimes return ResultSets where the scale of BigDecimals in a single column differs by row. The existing mapping requires exact match of scale to the target Arrow vector that was created based on ResultSetMetaData (or configuration), and when any row does not match exactly, an Exception is thrown.
> To support JDBC drivers where scale may be inconsistent by row, Arrow should allow a less-strict mode that coerces BigDecimals to target vectors with greater scale. The default strict behavior should be retained, but it may be useful to allow coercion to proper target scale.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)