DanielLeens commented on issue #12691: URL: https://github.com/apache/seatunnel/issues/12691#issuecomment-6082089964
Thanks — this is now a sufficiently concrete Blob-only contract to start the focused PR. It matches the current GCS extension pattern in `dev`: an additive configuration entry for checkpoint and IMap, an HDFS-backed checkpoint FileSystem configuration, and a dedicated IMap `CloudWriter` subtype so WAL updates do not depend on append/flush visibility. Keeping `azure.container` as the validated `wasb://`/`wasbs://` default-FS URI, rejecting `abfs`/`abfss`, and leaving all existing storage types unchanged are the correct boundaries. #12293 is an ADLS Connector-V2 PR with a failed Build; it neither overlaps this Zeta storage path nor removes the need for the Blob-specific tests here. Please make two details explicit in the PR. First, the supplied-runtime documentation must enumerate the exact compatible `hadoop-azure`/Azure SDK artifact set and versions needed in `lib/`, plus their license/NOTICE treatment; a test-scope POM entry only supports the test compilation and must not imply that the runtime jars are packaged. Second, keep the Azurite host-port requirement fully isolated in the test lifecycle, fail clearly if the required emulator endpoint is unavailable, and do not permit a real credential or endpoint to enter test output. The planned unit tests and the Azurite checkpoint plus new-instance/unclosed-IMap recovery tests are the right acceptance boundary. Please open one minimal PR with that complete configuration, runtime-loading, docs, and test chain, and link it here; do not fold ABFS/ADLS or a page-blob workaround into it. No issue metadata changed. -- 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]
