lhotari commented on issue #24588: URL: https://github.com/apache/pulsar/issues/24588#issuecomment-3138946790
> > [@wzhramc](https://github.com/wzhramc) Just curious, why are you targeting a Pulsar Sink and not a Pulsar Function? (transactional support is also missing there, but it would fit better in the existing abstractions) > > I'm encountering an issue where Pulsar Functions cannot effectively publish to two different topics simultaneously. In the Java Instance Implementation that underlies Pulsar Functions, sinks are used to handle message output, and these sinks rely on Pulsar producers to connect to the cluster and send messages. Taking inspiration from this architecture, I've created a custom sink with two producers that send messages to different topics concurrently. However, I need to ensure these operations are executed transactionally to maintain data consistency. This context is very useful that your actual use case would be solved with Pulsar Functions as long as it would support transactions. As mentioned in my previous message, transactions fit closer to the Pulsar Functions abstractions (interfaces). I'm aware of the implementation details. Implementation details can be adjusted, but we shouldn't break existing interfaces and abstractions when adding transactional support. @wzhramc How would you like to use transactions in Pulsar Functions? What would be the optimal interface change in your opinion? -- 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: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
