Someone just replied to the bug, it was already known about and will be fixed in the upcoming Iceberg 1.7.2 release.
On Thu, 2025-02-06 at 09:35 +0000, Aaron Grubb wrote: > Hi all, > > I filed a bug with the Iceberg team [1] but I'm not sure that it's 100% > specific to Iceberg (I assume it is as data in the related parquet > file is correct and session.read.parquet always returns correct results) so I > figured I would flag it here in case anyone has some insight. > Currently planning on trying different versions of Iceberg to see if I can > get correct results but this is a major blocker to my company's > infrastructure planning so any help would be appreciated. Maybe it's wiser to > try different Java versions or is it possible this is related > to using aarch64 somehow? All JARs are precompiled versions. > > Thanks, > Aaron > > [1] https://github.com/apache/iceberg/issues/12178 > > --------------------------------------------------------------------- > To unsubscribe e-mail: user-unsubscr...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe e-mail: user-unsubscr...@spark.apache.org
