[
https://issues.apache.org/jira/browse/BEAM-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407594#comment-16407594
]
Tim Robertson edited comment on BEAM-3201 at 3/21/18 9:05 AM:
--------------------------------------------------------------
This one has gone quiet and is pretty important (also for failure / retry
scenarios resulting in duplicate docs).
[~chet.aldrich] - can you please post an update of your intentions? Your GH
branch ([https://github.com/chetaldrich/beam/commits/beam-3201]) looks like it
is reasonably well progressed - is there anything we can do to help? I'd be
happy to pick it up from your branch if you want?
was (Author: timrobertson100):
This one has gone quiet and is pretty important (also for failure / retry
scenarios resulting in duplicate docs).
[~chet.aldrich] - can you please post an update of your intentions? Your GH
branch ([https://github.com/chetaldrich/beam/commits/beam-3201]) looks like it
is reasonably well progressed - is there anything we can do to help?
> ElasticsearchIO should allow the user to optionally pass id, type and index
> per document
> ----------------------------------------------------------------------------------------
>
> Key: BEAM-3201
> URL: https://issues.apache.org/jira/browse/BEAM-3201
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Reporter: Etienne Chauchot
> Assignee: Chet Aldrich
> Priority: Major
>
> *Dynamic documents id*: Today the ESIO only inserts the payload of the ES
> documents. Elasticsearch generates a document id for each record inserted. So
> each new insertion is considered as a new document. Users want to be able to
> update documents using the IO. So, for the write part of the IO, users should
> be able to provide a document id so that they could update already stored
> documents. Providing an id for the documents could also help the user on
> indempotency.
> *Dynamic ES type and ES index*: In some cases (streaming pipeline with high
> throughput) partitioning the PCollection to allow to plug to different ESIO
> instances (pointing to different index/type) is not very practical, the users
> would like to be able to set ES index/type per document.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)