You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Mark Norkin (JIRA)" <ji...@apache.org> on 2018/12/28 07:08:00 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 ]
Mark Norkin updated BEAM-6168:
------------------------------
Description:
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?
was:
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 a separate field and as part of _{{_source}}_.
Is there an option/workaround that would allow doing that?
> 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
> Assignee: Etienne Chauchot
> Priority: Major
>
> 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
(v7.6.3#76005)