GitHub user tzulitai opened a pull request:

    [FLINK-4988] [elasticsearch] Add Elasticsearch 5.x Connector

    This PR is based on @mikedias's work in #2767 (1st commit), with additional 
work to restructure the Elasticsearch connectors (2nd commit). Basically, we 
now have a `flink-connector-elasticsearch-base` containing common behaviour and 
test code.
    ### Deprecated Constructors for Elasticsearch 1.x / 2.x
    As part of the restructuring, all connector versions now take a 
`ElasticsearchSinkFunction` (previously, 1.x took a `IndexRequestBuilder`, 
which was limited to only indexing actions on a Elasticsearch index) for full 
functional Elasticsearch support.
    The `ElasticsearchSinkFunction` was also reallocated from pacakge 
`o.a.f.s.c.elasticsearch2` in `flink-connector-elasticsearch2`, to 
`o.a.f.s.c.elasticsearch` in `flink-connector-elasticsearch-base`.
    This resulted in deprecation of the following:
    1. In Elasticsearch 1.x: All original `IndexRequestBuilder` constructors as 
well as the interface itself have been deprecated.
    2. In Elasticsearch 2.x: Due to the package relocation of 
`ElasticsearchSinkFunction`, all original constructors are also deprecated in 
favor of the new package path for the class.
    R: @rmetzger @mikedias please feel free to review, thank you!

You can merge this pull request into a Git repository by running:

    $ git pull FLINK-4988

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3112
commit 746cbb4dd029837d9955cd3138444f70305ac542
Author: Mike Dias <>
Date:   2016-11-07T20:09:48Z

    [FLINK-4988] Elasticsearch 5.x support

commit 86482962b250899e9ac076768ff98bf8fbee58f8
Author: Tzu-Li (Gordon) Tai <>
Date:   2017-01-12T13:21:56Z

    [FLINK-4988] [elasticsearch] Restructure Elasticsearch connectors


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to