[FLINK-17483][legal] Update flink-sql-connector-elasticsearch7 NOTICE file to correctly reflect bundled dependencies

[carp84]

What is the purpose of the change

Fix the legal issue in flink-sql-connector-elasticsearch7 as reported by FLINK-17483

Brief change log

Update flink-sql-connector-elasticsearch7 NOTICE file to correctly reflect bundled dependencies, including:

• com.carrotsearch:hppc:0.8.1
• com.github.spullara.mustache.java:compiler:0.9.3
• org.elasticsearch:elasticsearch-geo:7.3.2
• org.elasticsearch.plugin:lang-mustache-client:7.3.2

Verifying this change

Manually compare the output of shaded plugin and the entries in the NOTICE file, make sure they are in accordance.

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/Mesos, 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)

[carp84]

CC @zentol @rmetzger

[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 4061d02 (Thu Apr 30 18:07:33 UTC 2020)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{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:

• 4061d02 Travis: SUCCESS

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

[rmetzger]

hppc has a NOTICE file that we need to forward: https://github.com/carrotsearch/hppc/blob/0.8.1/NOTICE.txt

I could not find it in this archive: https://repository.apache.org/content/repositories/orgapacheflink-1362/org/apache/flink/flink-sql-connector-elasticsearch7_2.11/1.10.1/flink-sql-connector-elasticsearch7_2.11-1.10.1.jar

[zentol]

Since the jar does not contain the NOTICE we do not have to forward it imo.

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file

[rmetzger]

Thanks a lot for this pointer! I learned something new about licenses tonight.

I rest my case.

[rmetzger]

Thanks a lot for addressing the licensing issues.

The added licenses are all ASL 2.0. I found one problem with the NOTICE file. Otherwise, the change is good to go

[zentol]

+1

Let's keep in mind that master will need an updated version since we use a different elasticsearch version there.

[rmetzger]

I'm +1 after consulting with Chesnay

[wuchong]

LGTM. Thanks @carp84 for working on this.

[carp84]

Thanks all for the review, and thanks @zentol for the reminder, will open another PR against master branch and watch the version updates of es.