chovy-3012 opened a new issue, #12697: URL: https://github.com/apache/seatunnel/issues/12697
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. > #7237 requested both source and sink, but was closed as completed with only the sink implemented. The source was never delivered. ### Description The `connector-activemq` module currently only provides a **sink** connector — there is no way to read messages from ActiveMQ queues into SeaTunnel pipelines. The original issue #7237 requested both source and sink, but was closed as completed with only the sink implemented; the source was never delivered. ### Usage Scenario Users who need to consume messages from ActiveMQ queues as a data source in SeaTunnel streaming pipelines, for example: - Reading events from an ActiveMQ queue and writing them to a database (JDBC sink) or data lake. - Consuming JSON-formatted domain events from ActiveMQ for real-time transformation and downstream delivery. - Using message selectors to filter messages on the broker side before they reach the pipeline. Example configuration: ```hocon env { parallelism = 1 job.mode = "STREAMING" } source { ActiveMQ { uri = "tcp://localhost:61616" username = "admin" password = "admin" queue_name = "testQueue" message_selector = "JMSType = 'car'" receive_timeout = 3000 schema = { fields { id = int name = string } } } } sink { Console {} } ``` ### Related issues - #7237 — Original request for ActiveMQ source/sink (closed as completed, only sink delivered) ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
