Github user cjolif commented on the issue:
https://github.com/apache/flink/pull/6043
@StephanEwen that is I think more or less what I proposed here:
https://lists.apache.org/thread.html/e7f584e0df9ce510fa5bee8d3a7e59b6df885f7deee36710a1cbb9b1@%3Cdev.flink.apache.org%3E
"In the hope of moving that forward I would like to propose for 1.6 a new
Elasticsearch 6.x+ sink that would follow the design of the previous ones
BUT only leverage the new REST API and not inherit from existing classes."
But @tzulitai hinted into a different direction, that I followed for this
PR.
Personally I think both approaches make sense. I don't have a strong
opinion. Even though for my personal use-cases just doing a separated REST
API-based sink would be enough.
---
