jakob-ed opened a new pull request #15152:
URL: https://github.com/apache/flink/pull/15152


   ## What is the purpose of the change
   
   Adds a source connector implementation following 
[FLIP-27](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95653748#FLIP27:RefactorSourceInterface-PublicInterface)
 to consume messages from Google Cloud Pub/Sub.
   
   ## Brief change log
   
   - Add basic Pub/Sub source using new interface
   - Add checkpointing and do some refactorings
   - Allow multiple records inside single Pub/Sub message for deserialization
   - Add Javadocs, README and clean up
   
   ## Verifying this change
   
   A new end-to-end test `EmulatedPubSubNewSourceTest.java` was added to verify 
these changes. However, currently the test never finishes and instead keeps 
waiting for new input records forever. The end-to-end test for the old source 
(`EmulatedPubSubSourceTest.java`) uses a stop marker mechanism to finish the 
test. I tried out different things to apply it to the new source end-to-end 
test but without success. Maybe you have an idea?
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (don't know)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (JavaDocs)
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to