You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/04 18:23:00 UTC
[jira] [Commented] (BEAM-11276) Write with custom indexName and docId not present in document itself
[ https://issues.apache.org/jira/browse/BEAM-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549030#comment-17549030 ]
Danny McCormick commented on BEAM-11276:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/20640
> Write with custom indexName and docId not present in document itself
> --------------------------------------------------------------------
>
> Key: BEAM-11276
> URL: https://issues.apache.org/jira/browse/BEAM-11276
> Project: Beam
> Issue Type: Wish
> Components: io-java-elasticsearch
> Affects Versions: 2.25.0
> Environment: Java, Google Dataflow
> Reporter: Lionel Setan
> Priority: P3
>
> ElasticIO connector write method is taking currently as input a "PCollection<String>" element ; string value will be passed as ElasticSearch document body. With methods withIdFn, and withIndexFn, we can overload Elastic document id and index name at runtime.
> There is some kind of situation where indexName and/or docId are not present in document itself (for example from Google Pubsub metadata or other).
> Is there a way to implement this usecase with current ElasticIO ? Otherwise, if it makes sense for you, what kind of improvment can be performed on connector ?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)