alpreu opened a new pull request #18038:
URL: https://github.com/apache/flink/pull/18038


   ## What is the purpose of the change
   
   We want to update the elasticsearch sink connectors to use the latest 
available minor version for Elasticsearch 6 and 7.
   
   
   ## Brief change log
   
     - flink-connector-elasticsearch-base and flink-connector-elasticsearch-7 
have been updated to Elasticsearch v7.15.2
     - flink-connector-elasticsearch-6 has been updated to Elasticsearch v6.8.20
     - Some classes (e.g. `TimeValue`) have been relocated by Elastic in 
between ES7 versions, therefore the `ElasticsearchApiCallBridge` for the old 
interface as well as the `ElasticsearchXSinkBuilder` for the new interfaces had 
to be changed to accommodate the different module locations of the class.
     - correct the connector docs to state that foe each major versions the 
connector is compatible across all minor versions
   
   
   ## Verifying this change
   
   This change is already covered by the existing tests, such as the modules 
unit tests and e2e tests.
   
   ## 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, 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.

To unsubscribe, e-mail: [email protected]

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


Reply via email to