SEZ9 commented on issue #11655: URL: https://github.com/apache/seatunnel/issues/11655#issuecomment-5215604252
Thanks for the well-scoped report. Since the root cause is a relocation mismatch, the fix likely belongs in the seatunnel-hadoop uber jar build: either also shade/relocate hadoop-aws (so its Jackson references are rewritten consistently) or stop relocating Jackson in the uber jar and manage the conflict differently. Could you paste the full stack trace (the exact ClassNotFoundException class name and the relocated package prefix)? That will confirm which Jackson artifacts need relocation coverage and help write a regression test. Noting the narrow blast radius: only S3A configs using fs.s3a.assumed.role.* / RoleModel are affected; plain access-key and instance-profile credentials are unaffected. Linking to #11648 where this was discovered during binary-compatibility analysis for the Hadoop 3.4.3 upgrade. <!-- streview-comment:62 --> -- 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]
