beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Etienne Chauchot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-3201) ElasticsearchIO should deal with documents id
Date Wed, 29 Nov 2017 10:56:00 GMT

    [ https://issues.apache.org/jira/browse/BEAM-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270589#comment-16270589
] 

Etienne Chauchot commented on BEAM-3201:
----------------------------------------

[~chet.aldrich] your summary is correct. I'll just precise 
{quote}
Each will require a function that takes in a JSON object and returns a String *value (from
the json element provided by the means the user choses)*, which is what will be placed in
the corresponding *ES bulk metadata place while inserting* .
{quote}

> ElasticsearchIO should deal with documents id
> ---------------------------------------------
>
>                 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
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message