parthchandra commented on issue #1714:
URL:
https://github.com/apache/datafusion-comet/issues/1714#issuecomment-2905098928
@huaxingao, fyi.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the sp
Kontinuation commented on issue #1714:
URL:
https://github.com/apache/datafusion-comet/issues/1714#issuecomment-2899728834
Iceberg 1.6.1 is known to cause segfault on Spark 3.5.4. See
https://github.com/apache/iceberg/pull/11731 and
https://github.com/apache/iceberg/issues/12178.
Yo
parthchandra commented on issue #1714:
URL:
https://github.com/apache/datafusion-comet/issues/1714#issuecomment-2860323801
> at �.wrap(ByteBufferInputStream.java:38)
Seems like memory got overwritten by some unsafe code which would be
consistent with getting a SEGV.
Just to
mixermt commented on issue #1714:
URL:
https://github.com/apache/datafusion-comet/issues/1714#issuecomment-2849354985
Another observation, failure happens while read of data from Iceberg table.
Either we have some versions mismatch, jar hell or some other still unknown
reason to me
mixermt commented on issue #1714:
URL:
https://github.com/apache/datafusion-comet/issues/1714#issuecomment-2849234775
Now I see that the failure occurred in a specific job from our regression
set.
I will try re-play it multiple times to narrow down the issue.
--
This is an automated
mixermt opened a new issue, #1714:
URL: https://github.com/apache/datafusion-comet/issues/1714
Hi,
Experience occasional failure of Spark executors
```
│ # A fatal error has been detected by the Java Runtime Environment:
