DanielLeens commented on issue #11620: URL: https://github.com/apache/seatunnel/issues/11620#issuecomment-5152722910
Thanks for the careful report and for pointing out the contract/runtime mismatch. I checked the current `dev` code path and this looks valid: 1. `PulsarBaseOptions.FORMAT` documents `text` and `field_delimiter`. 2. `PulsarSourceFactory` exposes `field_delimiter` when `format = text`. 3. `PulsarMultiTableConfig.validateFormat()` currently only allows `JSON`, `CANAL_JSON`, and `AVRO`. 4. `PulsarSource.createDeserialization()` also has no `TEXT` branch, so bypassing validation would still fail at runtime. I also checked for an obvious open PR covering Pulsar Source text support and did not find one. So the issue should be treated as a real Connector-V2 bug rather than only a documentation problem. The likely implementation path is: 1. decide whether `text` should be supported only for single-table Pulsar Source mode, while keeping the multi-table restriction explicit; 2. add the source-side text deserialization path using the existing text format support and `field_delimiter`; 3. add focused source factory/config tests and a deserialization test; 4. update both `docs/en` and `docs/zh` so the documented source behavior matches the runtime. I'll mark this as `bug` / `connectors-v2` / `help wanted`. A contributor can pick it up from the code paths above. -- 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]
