kekwan commented on issue #5970: URL: https://github.com/apache/iceberg/issues/5970#issuecomment-1314103802
We were able to resolve this issue. It was due to a classpath issue. @RussellSpitzer's tips on slack helped us find the issue: > We’ll the most common way this happens is just extra jars lying in classpaths that folks don’t realize are hanging out there. So I really do urge that you make sure the dependencies are there as expected. Usually I suggest using packages for distributing jars, but i think ```spark.jars``` does the same thing but without pulling in other dependencies. It’s been a while and since I don’t use .jars I’m not sure if that’s correct. > > If you are absolutely sure that it’s not an obvious old iceberg jar somewhere on the classpath, the next most likely thing is that someone has shaded a version of Iceberg into another library or has it as a shaded dependency. So while you wouldn’t see another Iceberg Jar the extra classfiles would still be included in some other jar. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
