[FLINK-19993] Remove flink-connector-filesystem module

[kl0u]

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)

[kl0u]

Still waiting for AZP to give the green light.

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit 88b2da1 (Thu Nov 05 09:55:27 UTC 2020)

Warnings:

• 4 pom.xml files were touched: Check for build and licensing issues.

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

Details

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• Unknown: CANCELED
• 5cba300 Azure: PENDING

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run travis re-run the last Travis build
• @flinkbot run azure re-run the last Azure build

[kl0u]

@flinkbot run azure

[dawidwys]

+1 for the PR once azure gives green. Had just one minor comment.

[dawidwys]

remove the comment as well

[kl0u]

Thanks for the review @dawidwys ! Merged