Hi Marco, The Java SDK connector for Apache PulsarIO is very demanded but, unfortunately, I’m not aware if anyone works on this (based on Jira discussion). So, feel free to take it!
One of the example, you may take a look on RabbitMqIO [1] that is quite straitforward in terms of implementation and it’s based on “old” UnboundedSource API for reading part. Though, for new connectors, it’s highly recommended to use new Splittable DoFn API [3] and one of the example could be KafkaIO and ReadFromKafkaViaSDF [2], but it might be a bit complicated if you are not very familiar with Beam codebase. Feel free to ask any questions here if you have more! — Alexey [1] https://github.com/apache/beam/blob/master/sdks/java/io/rabbitmq/src/main/java/org/apache/beam/sdk/io/rabbitmq/RabbitMqIO.java [2] https://github.com/apache/beam/blob/22205ee1a84581e9206c5c61bad88a799779b4bc/sdks/java/io/kafka/src/main/java/org/apache/beam/sdk/io/kafka/KafkaIO.java#L1344 [3] https://beam.apache.org/documentation/io/developing-io-java/ > On 29 Jun 2021, at 18:06, Marco Robles Pulido <marco.rob...@wizeline.com> > wrote: > > Hi everyone! > > I am planning to start working on this ticket BEAM-8218 > <https://issues.apache.org/jira/browse/BEAM-8218> - Implement Apache PulsarIO > Is there any example about what is about? or any progress on this topic? > > Thanks in advance, > -- > Marco Robles | WIZELINE > Software Engineer > marco.rob...@wizeline.com <mailto:marco.rob...@wizeline.com> > Amado Nervo 2200, Esfera P6, Col. Ciudad del Sol, 45050 Zapopan, Jal. > > This email and its contents (including any attachments) are being sent to > you on the condition of confidentiality and may be protected by legal > privilege. Access to this email by anyone other than the intended recipient > is unauthorized. If you are not the intended recipient, please immediately > notify the sender by replying to this message and delete the material > immediately from your system. Any further use, dissemination, distribution > or reproduction of this email is strictly prohibited. Further, no > representation is made with respect to any content contained in this email.
