DanielLeens commented on issue #10883: URL: https://github.com/apache/seatunnel/issues/10883#issuecomment-4436398283
Thanks for the detailed investigation and for checking both the release artifact and the source tree. I rechecked the current `dev` packaging path, and this does look like a real release-packaging issue. The key path is: - `seatunnel-engine-server` still declares `imap-storage-file` as a runtime dependency; - `FileMapStore` loads the storage implementation through `IMapStorageFactory` discovery based on `type`; - but the binary assembly only copies starter jars and connector jars into the release package, and I do not see `imap-storage-file` being added to the released distribution. So the documented `map-store` configuration can point to a valid implementation in source code, while the binary release still cannot load it out of the box. That part is enough to keep this issue open as a genuine bug. One detail I would separate from the confirmed packaging gap: the current startup scripts only build the server classpath from `/lib/*` plus the starter jar. I do not see a dedicated `plugins/imap-storage-plugins` loading path there. So if a matching-version `imap-storage-file` jar was manually added to `/lib` and still did not load, please share the master startup log around MapStore / storage initialization and the exact jar list under `/lib`. That would help confirm whether there is a second runtime problem beyond the already confirmed release-package omission. Thanks again for narrowing this down so clearly. -- 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]
