Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3112
While rebasing #2861 on the restructured ES connectors in this PR, I jumped
around different options on whether or not the `BulkProcessor` build process
should be abstracted. In the end, I think it will still be best to keep that
abstracted to keep duplicated code to the minimum.
To bridge the error logging problem, I introduced a
`ElasticsearchApiCallBridge` interface to solve this. This call bridge can be
further extended for other incompatible APIs that we bump into in the future.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
