You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Alexey Romanenko (JIRA)" <ji...@apache.org> on 2019/08/08 11:44:00 UTC
[jira] [Updated] (BEAM-7916) Add ElasticsearchIO query parameter to
take a ValueProvider
[ https://issues.apache.org/jira/browse/BEAM-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Romanenko updated BEAM-7916:
-----------------------------------
Summary: Add ElasticsearchIO query parameter to take a ValueProvider (was: Change ElasticsearchIO query parameter to be a ValueProvider)
> Add ElasticsearchIO query parameter to take a ValueProvider
> -----------------------------------------------------------
>
> Key: BEAM-7916
> URL: https://issues.apache.org/jira/browse/BEAM-7916
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Affects Versions: 2.14.0
> Reporter: Oliver Henlich
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We need to be able to perform Elasticsearch queries that are dynamic. The problem is {{ElasticsearchIO.read().withQuery()}} only accepts a string which means the query must be known when the pipleline/Google Dataflow Template is built.
> It would be great if we could change the parameter on the {{withQuery()}} method from {{String}} to {{ValueProvider<String>}}.
> Pull request: https://github.com/apache/beam/pull/9285
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)