You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jeroen Steggink (JIRA)" <ji...@apache.org> on 2018/01/16 14:25:00 UTC
[jira] [Commented] (BEAM-3201) ElasticsearchIO should allow the
user to optionally pass id, type and index per document
[ https://issues.apache.org/jira/browse/BEAM-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327160#comment-16327160 ]
Jeroen Steggink commented on BEAM-3201:
---------------------------------------
Hi, what's the status for this issue? It's quite an important feature to be able to overwrite existing documents in the index. Can I be of any help? Code review?
> 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: sdk-java-extensions
> 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)