You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:25 UTC

[jira] [Updated] (BEAM-6168) Allow modification of JSON value before writing to ElasticSearch

     [ https://issues.apache.org/jira/browse/BEAM-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Beam JIRA Bot updated BEAM-6168:
--------------------------------
    Labels: stale-P2  (was: )

> Allow modification of JSON value before writing to ElasticSearch
> ----------------------------------------------------------------
>
>                 Key: BEAM-6168
>                 URL: https://issues.apache.org/jira/browse/BEAM-6168
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-elasticsearch
>            Reporter: Mark Norkin
>            Priority: P2
>              Labels: stale-P2
>
> I have an Apache Beam streaming job which reads data from Kafka and writes to ElasticSearch using ElasticSearchIO.
> The issue I'm having is that messages in Kafka already have _{{key}}_ field, and using {{ElasticSearchIO.Write.withIdFn()}} I'm mapping this field to document _{{_id}}_ field in ElasticSearch.
> Having a big volume of data I don't want the _{{key}}_ field to be also written to ElasticSearch as part of _{{_source}}_.
> Is there an option/workaround that would allow doing that?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)