[
https://issues.apache.org/jira/browse/BEAM-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493494#comment-16493494
]
Jeroen Steggink commented on BEAM-3199:
---------------------------------------
I have been working on a specific IO for Elasticsearch 6.x. It can be found
here:
[https://github.com/jsteggink/beam/tree/BEAM-3199]
Since people would still use the old ES versions (2.x and 5.x), it's a separate
Maven module (elasticsearch-6). Furthermore, it tries to use the
RestHighLevelClient where it can. This means a lot can be abstracted and
optimizations can be done by ES. There are no more strings containing json, but
uses ES objects for both Read and Write.
I'm still working on the Read parts and the integration tests. The integration
tests require a lot of refactoring, since the use of ESIntegTestCase with the
new RestHighLevelClient is not ideal. I would rather just do my own integration
tests based on ElasticsearchIO and a live ES cluster using Docker or with
Kubernetes.
Any help and review is welcome!
> Upgrade to Elasticsearch 6.x
> ----------------------------
>
> Key: BEAM-3199
> URL: https://issues.apache.org/jira/browse/BEAM-3199
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> Elasticsearch 6.x is now GA. As it's fully compatible with Elasticsearch 5.x,
> it makes sense to upgrade.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
