Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/6043
One more thing to clarify:
When planning to switch to REST, are we speaking of an implementation that
works directly against Elasticsearch's REST API? Or are we thinking of using
Elasticsearch's
[RestHighLevelClient](https://snapshots.elastic.co/javadoc/org/elasticsearch/client/elasticsearch-rest-high-level-client/7.0.0-alpha1-SNAPSHOT/org/elasticsearch/client/RestHighLevelClient.html)?
I would assume the latter, but IMO we would not be able to avoid yet again
having a common base module across future versions (e.g. across ES 6.x, 7.x,
and so on), even if we make a clean cut now.
So, I have the feeling that the main problem here isn't that we are sharing
code between versions, but the fact that our base shared code isn't
future-proof enough for potential 3rd party API breaks.
That's the main reason why I'm proposing not to expose Elasticsearch
classes anymore through base class APIs in the shared module.
---
