Hi everyone, We're looking for community members, who would like to maintain Flink's Google PubSub connector [1] going forward. There are multiple improvement tickets open and the original contributors are currently unable to work on further improvements.
An overview of some of the open tickets: * https://issues.apache.org/jira/browse/FLINK-20625 -> Refactor PubSub Source to use new Source API (FLIP-27) * https://issues.apache.org/jira/browse/FLINK-24298 -> Refactor PubSub Sink to use new Sink API (FLIP-143 / FLIP-171) * https://issues.apache.org/jira/browse/FLINK-24299 -> Make PubSub available as Source and Sink for Table/SQL users Next to these tickets, the connector only supports Java 8 and we can improve on the tests for this connector. If you would like to take on this responsibility or can join this effort in a supporting role, please reach out! If we can't find maintainers for this connector, what do you think we should do? I would be in favour of dropping the connector from Flink. We could also consider moving the connector, either to the new external connector repository or Apache Bahir. I'm not sure if that would be valuable, since at some point connector won't work in Flink (since it doesn't use the target interfaces) and the source code can still be found in Flink's git repo by looking back to previous versions. I'm looking forward to your thoughts. Best regards, Martijn Visser [1] https://nightlies.apache.org/flink/flink-docs-stable/docs/connectors/datastream/pubsub/
