Hello Gunnar, Thanks for the message and willingness to collaborate. Most connectors on Beam are called based on the target system name + the IO suffix, e.g. KafkaIO, PubsubIO, KinesisIO, etc. so naming it DebeziumIO makes sense from the Beam side. So far nobody has requested us to rename a Beam connector because it is assumed that if the code of the connector resides on the Apache project repository the maintenance comes from the Beam community.
I don't know what others in the community think, I suppose it is still possible to rename it since the component has not been released yet, it will be released on Beam 2.29.0 (branch cut tomorrow). The real deal is what name would be appropriate that allows users to find it easily, specially as a single word name. Any suggestions? Or would making it clear in the component documentation + webpage that this component is not developed by the Debezium project be enough for the Debezium community so we (Beam) can use the name? Best, Ismaël On Tue, Mar 9, 2021 at 12:09 PM Gunnar Morling <[email protected]> wrote: > > Hi, > > I'm the lead of the Debezium project and just saw that the Apache Beam > community is working on integrating Debezium into Beam. That's really > exciting. and I'd love to see a demo of this. If there's anything the > Debezium community can do in order to help with this, please let us know on > the Debezium mailing list [1]. > > What I'd like to kindly ask for though is finding a name for this component > other than "DebeziumIO", as currently used in the README [2]. This may > suggest that this is an effort by the Debezium community itself, and we > should avoid any potential confusion here. A name like "Apache Beam connector > for Debezium" would be fine. > > Thanks a lot, > > --Gunnar > > [1] https://groups.google.com/g/debezium > [2] https://github.com/apache/beam/tree/master/sdks/java/io/debezium/src >
