[
https://issues.apache.org/jira/browse/FLINK-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149875#comment-16149875
]
Mike Dias commented on FLINK-7430:
--
What I see about FLINK-6833 is solution for a corner-case that maybe
[
https://issues.apache.org/jira/browse/FLINK-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16149283#comment-16149283
]
Mike Dias commented on FLINK-7430:
--
Perhaps the solution is revert the code implemented in FLINK-6833
Mike Dias created FLINK-4988:
Summary: Elasticsearch 5.x support
Key: FLINK-4988
URL: https://issues.apache.org/jira/browse/FLINK-4988
Project: Flink
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/FLINK-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Dias closed FLINK-4885.
Resolution: Invalid
I just realized that these optimizations aren't doable because:
- The missing
[
https://issues.apache.org/jira/browse/FLINK-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15598518#comment-15598518
]
Mike Dias commented on FLINK-4491:
--
Unfortunately, no. If you are using ES 2.x, you only can use
Mike Dias created FLINK-4885:
Summary: Improve the Elasticsearch configuration flexibility
Key: FLINK-4885
URL: https://issues.apache.org/jira/browse/FLINK-4885
Project: Flink
Issue Type:
[
https://issues.apache.org/jira/browse/FLINK-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15597296#comment-15597296
]
Mike Dias commented on FLINK-4491:
--
Hi Flavio, I think that this is better addressed by using [Indices
