[ 
https://issues.apache.org/jira/browse/BEAM-7916?focusedWorklogId=291988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-291988
 ]

ASF GitHub Bot logged work on BEAM-7916:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Aug/19 10:32
            Start Date: 09/Aug/19 10:32
    Worklog Time Spent: 10m 
      Work Description: aromanenko-dev commented on pull request #9305: Revert 
"[BEAM-7916] Add ElasticsearchIO query parameter to take a ValueProvider"
URL: https://github.com/apache/beam/pull/9305
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 291988)
    Time Spent: 2h  (was: 1h 50m)

> 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
>            Assignee: Alexey Romanenko
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h
>  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)

Reply via email to