nastra commented on issue #9960: URL: https://github.com/apache/iceberg/issues/9960#issuecomment-2681166064
I looked into this with a fresh Spark 3.5.4 installation and using Iceberg 1.5.0 against a REST catalog and I'm not able to reproduce this issue. [SPARK-43324](https://github.com/apache/spark/pull/41028) added UPDATE handling to Spark 3.5. At the same time, UPDATE handling was removed from Iceberg's Spark 3.5 runtime module (because it's now completely handled by Spark). There are a few things that would cause this issue * running the UPDATE against a non-Iceberg table would cause this issue * there is a risk that this might be caused due to mixed iceberg-spark-runtime dependencies on the classpath. If you're upgrading from an older version, make sure Spark's **jars** folder doesn't contain any old dependencies. Double-check this by using a fresh Spark installation * there's the possibility that something isn't properly handled in Spark itself for this For people that commented on this issue here, can you please double-check whether you have duplicate/old dependencies on the classpath? -- 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 specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
