[ https://issues.apache.org/jira/browse/BEAM-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547421#comment-17547421 ]
Kenneth Knowles commented on BEAM-6168: --------------------------------------- This issue has been migrated to https://github.com/apache/beam/issues/19182 > 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: P3 > > 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.20.7#820007)