Yanquan Lv created FLINK-37200:
--
Summary: Add e2e test for ElasticSearch Sink.
Key: FLINK-37200
URL: https://issues.apache.org/jira/browse/FLINK-37200
Project: Flink
Issue Type: Improvement
JunboWang created FLINK-36559:
-
Summary: [docs]Add elasticsearch sink to docs
Key: FLINK-36559
URL: https://issues.apache.org/jira/browse/FLINK-36559
Project: Flink
Issue Type: Improvement
wuzexian created FLINK-35894:
Summary: Add Elasticsearch Sink Connector for Flink CDC Pipeline
Key: FLINK-35894
URL: https://issues.apache.org/jira/browse/FLINK-35894
Project: Flink
Issue Type
Tudor Plugaru created FLINK-32028:
-
Summary: Error handling for ElasticSearch sink
Key: FLINK-32028
URL: https://issues.apache.org/jira/browse/FLINK-32028
Project: Flink
Issue Type
Alexander Preuss created FLINK-26638:
Summary: Reintroduce ActionFailureHandler for Elasticsearch sink
connectors
Key: FLINK-26638
URL: https://issues.apache.org/jira/browse/FLINK-26638
Project
Fabian Paul created FLINK-25571:
---
Summary: Update Elasticsearch Sink to use decomposed interfaces
Key: FLINK-25571
URL: https://issues.apache.org/jira/browse/FLINK-25571
Project: Flink
Issue
Alexander Preuss created FLINK-24323:
Summary: Port ElasticSearch Sink to new Unified Sink API (FLIP-143)
Key: FLINK-24323
URL: https://issues.apache.org/jira/browse/FLINK-24323
Project: Flink
McClone created FLINK-19115:
---
Summary: Null value fields cannot be ignored in ElasticSearch Sink
Key: FLINK-19115
URL: https://issues.apache.org/jira/browse/FLINK-19115
Project: Flink
Issue Type
rinkako created FLINK-18359:
---
Summary: Improve error-log strategy for Elasticsearch sink for
large data documentId conflict when using create mode for `insert ignore`
semantics
Key: FLINK-18359
URL: https
Jark Wu created FLINK-18093:
---
Summary: E2E tests manually for Elasticsearch Sink
Key: FLINK-18093
URL: https://issues.apache.org/jira/browse/FLINK-18093
Project: Flink
Issue Type: Sub-task
Yun Wang created FLINK-17623:
Summary: Elasticsearch sink should support user resource cleanup
Key: FLINK-17623
URL: https://issues.apache.org/jira/browse/FLINK-17623
Project: Flink
Issue Type
Kai Chen created FLINK-17116:
Summary: support UsernamePasswordCredentials for elasticsearch
sink via SQL DDL
Key: FLINK-17116
URL: https://issues.apache.org/jira/browse/FLINK-17116
Project: Flink
YangLee created FLINK-16736:
---
Summary: Expose Elasticsearch sink metric
Key: FLINK-16736
URL: https://issues.apache.org/jira/browse/FLINK-16736
Project: Flink
Issue Type: Improvement
Leonard Xu created FLINK-16701:
--
Summary: Elasticsearch sink support alias for indices.
Key: FLINK-16701
URL: https://issues.apache.org/jira/browse/FLINK-16701
Project: Flink
Issue Type
Jark Wu created FLINK-16495:
---
Summary: Improve default flush strategy for Elasticsearch sink to
make it work out-of-box
Key: FLINK-16495
URL: https://issues.apache.org/jira/browse/FLINK-16495
Project
ouyangwulin created FLINK-15400:
---
Summary: elasticsearch sink support dynamic index.
Key: FLINK-15400
URL: https://issues.apache.org/jira/browse/FLINK-15400
Project: Flink
Issue Type: New
By default, flushOnCheckpoint is set to True.
So ideally, based on env.enableCheckpointing(30); the flush to ES
must be triggered every 30seconds, though our ES Flush timeout is 60
seconds.
If the above assumption is correct, then still we do not see packets
getting flushed till the next p
Yes, we do maintain checkpoints
env.enableCheckpointing(30);
But we assumed it is for Kafka consumer offsets. Not sure how this is
useful in this case? Can you pls. elaborate on this.
~Ramya.
On Fri, Jun 21, 2019 at 4:33 PM miki haiat wrote:
> Did you set some checkpoints configuration?
Did you set some checkpoints configuration?
On Fri, Jun 21, 2019, 13:17 Ramya Ramamurthy wrote:
> Hi,
>
> We use Kafka->Flink->Elasticsearch in our project.
> The data to the elasticsearch is not getting flushed, till the next batch
> arrives.
> E.g.: If the first batch contains 1000 packets, t
Hi,
We use Kafka->Flink->Elasticsearch in our project.
The data to the elasticsearch is not getting flushed, till the next batch
arrives.
E.g.: If the first batch contains 1000 packets, this gets pushed to the
Elastic, only after the next batch arrives [irrespective of reaching the
batch time limi
e
>> >
>> > specifically for 5.3+ and 6.x+, which we've also agreed on the PR isn't
>> a
>> > nice way to go.
>> >
>> > So if I read you correctly you are ok moving with a proper fix but it
>> > should not introduce a new (RES
support for ES 1.x and 2.x starting from
> 1.6. Those are very old ES versions (considering that ES 6.x has already
> been out for a while). Do you think this would simply how our base module
> APIs are designed?
> - Wouldn't it be possible to have a REST implementation of the
>
> >
> > Thanks for bringing this up.
> >
> > Yes, the main issue with the existing PRs and preventing it from moving
> > forward is how it currently breaks initial assumptions of APIs in the
> > `elasticsearch-base` module.
> > Working around that would require intro
ing from
> 1.6. Those are very old ES versions (considering that ES 6.x has already
> been out for a while). Do you think this would simply how our base module
> APIs are designed?
> - Wouldn't it be possible to have a REST implementation of the
> `ElasticsearchSinkCall
with a proper fix.
>
> Some other remarks / questions I have:
> - Maybe we can consider removing support for ES 1.x and 2.x starting from
> 1.6. Those are very old ES versions (considering that ES 6.x has already
> been out for a while). Do you think this would simply how our base mod
remove ES 1.x and 2.x, it might actually be possible to completely
replace the current `elasticsearch-base` module.
Cheers,
Gordon
On Sun, May 13, 2018 at 12:36 AM, Flavio Pompermaier wrote:
Hi all,
There is quite some time Flink Elasticsearch sink is broken for
Elastisearch 5.x (nearly
AM, Flavio Pompermaier wrote:
Hi all,
There is quite some time Flink Elasticsearch sink is broken for
Elastisearch 5.x (nearly a year):
https://issues.apache.org/jira/browse/FLINK-7386
And there is no support for Elasticsearch 6.x:
https://issues.apache.org/jira/browse/FLINK-8101
However se
.x (covering both 5.2 and 5.3+)? If so,
> once we remove ES 1.x and 2.x, it might actually be possible to completely
> replace the current `elasticsearch-base` module.
>
> Cheers,
> Gordon
>
>
> On Sun, May 13, 2018 at 12:36 AM, Flavio Pompermaier >
> wrote:
>
> &
don
On Sun, May 13, 2018 at 12:36 AM, Flavio Pompermaier
wrote:
> +1. Torally agree
>
> On Sat, 12 May 2018, 18:14 Christophe Jolif, wrote:
>
> > Hi all,
> >
> > There is quite some time Flink Elasticsearch sink is broken for
> > Elastisearch 5.x (nearly a ye
+1. Torally agree
On Sat, 12 May 2018, 18:14 Christophe Jolif, wrote:
> Hi all,
>
> There is quite some time Flink Elasticsearch sink is broken for
> Elastisearch 5.x (nearly a year):
>
> https://issues.apache.org/jira/browse/FLINK-7386
>
> And there is no suppo
Hi all,
There is quite some time Flink Elasticsearch sink is broken for
Elastisearch 5.x (nearly a year):
https://issues.apache.org/jira/browse/FLINK-7386
And there is no support for Elasticsearch 6.x:
https://issues.apache.org/jira/browse/FLINK-8101
However several PRs were issued:
https
Hai Zhou UTC+8 created FLINK-7697:
-
Summary: Add metrics for Elasticsearch Sink
Key: FLINK-7697
URL: https://issues.apache.org/jira/browse/FLINK-7697
Project: Flink
Issue Type: Wish
Flavio Pompermaier created FLINK-5353:
-
Summary: Elasticsearch Sink loses well-formed documents when there
are malformed documents
Key: FLINK-5353
URL: https://issues.apache.org/jira/browse/FLINK-5353
static-max created FLINK-5122:
-
Summary: Elasticsearch Sink loses documents when cluster has high
load
Key: FLINK-5122
URL: https://issues.apache.org/jira/browse/FLINK-5122
Project: Flink
Issue
34 matches
Mail list logo
