[
https://issues.apache.org/jira/browse/BEAM-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Etienne Chauchot updated BEAM-3201:
-----------------------------------
Description:
*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.
was:
*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
> 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
>
> *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
(v6.4.14#64029)
