You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Krisztian Szucs (Jira)" <ji...@apache.org> on 2019/09/30 13:50:00 UTC
[jira] [Updated] (ARROW-6218) [Java] Add UINT type test in
integration to avoid potential overflow
[ https://issues.apache.org/jira/browse/ARROW-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krisztian Szucs updated ARROW-6218:
-----------------------------------
Fix Version/s: (was: 1.0.0)
0.15.0
> [Java] Add UINT type test in integration to avoid potential overflow
> --------------------------------------------------------------------
>
> Key: ARROW-6218
> URL: https://issues.apache.org/jira/browse/ARROW-6218
> Project: Apache Arrow
> Issue Type: Test
> Components: Java
> Reporter: Ji Liu
> Assignee: Ji Liu
> Priority: Critical
> Labels: pull-request-available
> Fix For: 0.15.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> As per discussion [https://github.com/apache/arrow/pull/5002]
> For UINT type, when write/read json data in integration test, it extend data type(i.e. Long->BigInteger, Int->Long) to avoid potential overflow.
> Like UINT8 the write side and read side code like this:
>
> {code:java}
> case UINT8:
> generator.writeNumber(UInt8Vector.getNoOverflow(buffer, index));
> break;{code}
>
> {code:java}
> BigInteger value = parser.getBigIntegerValue();
> buf.writeLong(value.longValue());
> {code}
> Should add a test to avoid potential overflow in the data transfer process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)