DanielLeens commented on PR #11902: URL: https://github.com/apache/seatunnel/pull/11902#issuecomment-5492865458
Thanks @davidzollo — confirming the same on the merge-conflict side: `mergeStateStatus` is currently `DIRTY` (`mergeable: CONFLICTING`) against `dev` for this branch. That said, per the discussion above with @goutamadwant, a plain rebase alone won't close this out. The real blocker is still the one we traced on 2026-08-22: `dev` no longer vendors a `seatunnel-shade` reactor module, so declaring `hadoop-azure` directly here would pull unrelocated Guava/Jackson/HTTP transitively into the connector package. The clean path is still to add `hadoop-azure` + the ABFS service entries to the external `apache/seatunnel-shade` repo's Hadoop 3 uber artifact first, get that published/bumped, and only then rebase this PR to consume the updated shade artifact and resolve the conflicts. @goutamadwant, let me know if you'd like help scoping the `seatunnel-shade` side of that change, or if it's already in progress. -- 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]
