DanielLeens commented on issue #10172: URL: https://github.com/apache/seatunnel/issues/10172#issuecomment-5509300693
Thanks for volunteering. Please do not add a call-site compatibility guard for Hadoop 3.1.x versus 3.3.x. The existing open PR #11823 already covers this issue across the plain, Kerberos, and proxy-user FileSystem initialization paths; it deliberately improves the LinkageError diagnostic without claiming to make mismatched Hadoop client jars compatible. A real compatibility feature would need an isolated dependency or classloading design, not a guard around FsTracer. Please review or test #11823 and add concrete feedback there rather than opening a competing implementation. -- 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]
