MartijnVisser opened a new pull request, #21501:
URL: https://github.com/apache/flink/pull/21501

   ## What is the purpose of the change
   
   The Pulsar connector code has been moved to 
https://github.com/apache/flink-connector-pulsar. 
   * The `3.0` branch contains the 1.16 code. There's currently a vote ongoing 
to officially release that. 
   * The current `main` branch contains the code from this repo's `master` 
branch. 
   
   I believe we can already remove the code from the repository, because the 
current code from `master` (or `main` if you look at the externalized connector 
repo) is a breaking change compared to the Flink 1.16 release and can only be 
released when Flink 1.17 has been released. Given that circumstances plus the 
instability of the Pulsar connector on the overall Flink CI stability would 
make it good to already remove the connector. 
   
   ## Brief change log
   
   * Removed all source code, documentation and references
   * Updated the Python code to refer to the externalized connector version
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
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: [email protected]

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

Reply via email to