Skip to content

Conversation

@tianchen92
Copy link
Contributor

Related to ARROW-1875.
This is Java side implementation.

@emkornfield
Copy link
Contributor

It is surprising that this passes, I will need to check it out and run it locally to make sure something funny isn't happening. But then i think it can be merged.

@emkornfield emkornfield self-requested a review August 9, 2019 03:00
@emkornfield emkornfield self-assigned this Aug 9, 2019
@tianchen92
Copy link
Contributor Author

It is surprising that this passes, I will need to check it out and run it locally to make sure something funny isn't happening. But then i think it can be merged.

Hi Micah, Anything found?

praveenbingo pushed a commit that referenced this pull request Aug 13, 2019
…al overflow

Related to [ARROW-6218](https://issues.apache.org/jira/browse/ARROW-6218).
As per discussion #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:
>case UINT8:
  generator.writeNumber(UInt8Vector.getNoOverflow(buffer, index));
  break;

>BigInteger value = parser.getBigIntegerValue();
buf.writeLong(value.longValue());

Should add a test to avoid potential overflow in the data transfer process.

Closes #5072 from tianchen92/ARROW-6218 and squashes the following commits:

2bdbe7e <tianchen> use MIN_VALUE and MAX_VALUE
1430979 <tianchen> ARROW-6218:  Add UINT type test in integration to avoid potential overflow

Authored-by: tianchen <niki.lj@alibaba-inc.com>
Signed-off-by: Praveen <praveen@dremio.com>
@emkornfield
Copy link
Contributor

OK, the reason why this doesn't break other languages is the integration tests don't seem to actually use the write path (arrow->json), and the read path (json->arrow) is robust to either strings or numbers. So I think this can be merged. And we can have other languages make similar changes and then change the python script.

CC @wesm

@emkornfield
Copy link
Contributor

+1 thank you.

pribor pushed a commit to GlobalWebIndex/arrow that referenced this pull request Oct 24, 2025
…al overflow

Related to [ARROW-6218](https://issues.apache.org/jira/browse/ARROW-6218).
As per discussion apache#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:
>case UINT8:
  generator.writeNumber(UInt8Vector.getNoOverflow(buffer, index));
  break;

>BigInteger value = parser.getBigIntegerValue();
buf.writeLong(value.longValue());

Should add a test to avoid potential overflow in the data transfer process.

Closes apache#5072 from tianchen92/ARROW-6218 and squashes the following commits:

2bdbe7e <tianchen> use MIN_VALUE and MAX_VALUE
1430979 <tianchen> ARROW-6218:  Add UINT type test in integration to avoid potential overflow

Authored-by: tianchen <niki.lj@alibaba-inc.com>
Signed-off-by: Praveen <praveen@dremio.com>
pribor pushed a commit to GlobalWebIndex/arrow that referenced this pull request Oct 24, 2025
…SON files

Related to [ARROW-1875](https://issues.apache.org/jira/browse/ARROW-1875).
This is Java side implementation.

Closes apache#5002 from tianchen92/ARROW-1875 and squashes the following commits:

20cc581 <tianchen> ARROW-1875:  Write 64-bit ints as strings in integration test JSON files

Authored-by: tianchen <niki.lj@alibaba-inc.com>
Signed-off-by: Micah Kornfield <emkornfield@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants