[
https://issues.apache.org/jira/browse/BEAM-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732785#comment-16732785
]
Mark Norkin commented on BEAM-6168:
-----------------------------------
Thank you explanation, got your point now.
I understand the downside you described, and yes it is safe to say that it will
slow down connector by some degree. However this is totally seen as an opt-in
functionality, which user may or may not want to use and so there won't be any
additional slowness if user would decide to opt-out on it.
In any case if you decide to not support this use-case I would understand.
> 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)
