Github user fpompermaier commented on the issue: https://github.com/apache/flink/pull/2790 From my point of view ElasticSearchHelper is very useful if you plan to use the Flink Elasticsearch Sink in a real production use case, because it reduce a lot the complexity of interfacing with ES. We didn't use ES java client before and it took about 2 days to write that helper...I think it's not that obvious to rewrite that logic from the scratch. Ina production environment you really needs to easy customize indexing templates and mappings IMHO
--- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---