Parth Chandra

> at �.wrap(ByteBufferInputStream.java:38) Seems like memory got overwritten by some unsafe code which would be consistent with getting a SEGV. Just to eliminate the possibility, what compression type are you...

Hmm, I am not aware of any issues related to zstd so that's probably not it. This is clearly an issue but hard to address without being able to reproduce....

@huaxingao, fyi.

A good test would be to write with this feature enabled and then read it with and without Comet enabled.

You may want to undo parts of https://github.com/apache/datafusion-comet/pull/1376 to really test the change. The changes to `CometTestBase.getPrimitiveTypesParquetSchema` were so that the schema would not contain unsigned types if the reader...

I seem to recall that I tested a `badly` written file with https://github.com/apache/arrow/issues/7055 and did _not_ get garbage. I'll take a look at it again. Thanks for kicking off this...

Surprising that Postgres fails. According to the [docs](https://www.postgresql.org/docs/8.2/datatype-numeric.html), `Infinity, -Infinity, and NaN` are legitimate floating point values. This is also the expected behavior per the ANSI SQL standard, afaik. `NULL`...

> ```shell > ERROR: division by zero > ``` I wasn't doubting it. :) But I am surprised. @comphead I'll take back my 'NULL is not the right thing to...