[ 
https://issues.apache.org/jira/browse/BEAM-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353803#comment-17353803
 ] 

Beam JIRA Bot commented on BEAM-11283:
--------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 
days. It is now automatically moved to P3. If you are still affected by it, you 
can comment and move it back to P2.

> Allow for Parent parameter for Parent/Child join - ElasticsearchIO
> ------------------------------------------------------------------
>
>                 Key: BEAM-11283
>                 URL: https://issues.apache.org/jira/browse/BEAM-11283
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-elasticsearch
>    Affects Versions: 2.25.0
>            Reporter: Robert Coe
>            Priority: P3
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> It is impossible to index Parent/Child documents using ElasticsearchIO
>  
> When using parent/child documents in Elasticsearch, child documents must be 
> indexed using the "parent" attribute when using the bulk endpoint.
>  
> [https://www.elastic.co/guide/en/elasticsearch/guide/master/indexing-parent-child.html]
> [https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-bulk.html]
>  
> [https://github.com/apache/beam/blob/master/sdks/java/io/elasticsearch/src/main/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIO.java]
> There needs to be a "parent" attribute on the DocumentMetadata object. I 
> think a FieldValueExtractFn would work really nicely for this
>  



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

Reply via email to