kl0u opened a new pull request #13941:
URL: https://github.com/apache/flink/pull/13941


   ## What is the purpose of the change
   
   The flink-connector-filesystem module contains (only) the deprecated 
BucketingSink. The BucketingSink. The sink is deprecated since FLINK 1.9 in 
favour of the relatively recently introduced StreamingFileSink.
   
   For the sake of a clean and more manageable codebase, the community chose to 
remove it [1] after the discussion in [2].
   
   [1]
   
https://lists.apache.org/thread.html/red2bc04c5d60a6a923ea499a49d7889d66661c31ac1987ea6d9a3fe5%40%3Cdev.flink.apache.org%3E
   [2] 
https://lists.apache.org/thread.html/re24ceedc02402ac9a6ce1e07b690852320a265b081f416ebac543aaf%40%3Cuser.flink.apache.org%3E
   
   ## Brief change log
   
   Removed the module itself and wherever it appeared in the documentation.
   
   ## Verifying this change
   
   This change is a 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): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (**yes** / no)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / 
don't know)
     - The S3 file system connector: (**yes** / no / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   


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