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

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

                Author: ASF GitHub Bot
            Created on: 12/Mar/20 17:15
            Start Date: 12/Mar/20 17:15
    Worklog Time Spent: 10m 
      Work Description: kamilwu commented on issue #11040: [BEAM-9305] Allow 
value provider query strings in _CustomBigQuerySource
URL: https://github.com/apache/beam/pull/11040#issuecomment-598308988
 
 
   >  Is that a bug then?
   
   Yes, this might be a bug. I don't know a good solution at the moment 
though... this is more complicated, because we have to fallback to 
temp_location from pipeline options if gcs_location is empty
 
----------------------------------------------------------------
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: 402325)
    Time Spent: 3h 20m  (was: 3h 10m)

> Support ValueProvider for BigQuerySource query string
> -----------------------------------------------------
>
>                 Key: BEAM-9305
>                 URL: https://issues.apache.org/jira/browse/BEAM-9305
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-py-gcp
>            Reporter: Elias Djurfeldt
>            Assignee: Elias Djurfeldt
>            Priority: Minor
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Users should be able to use ValueProviders for the query string in 
> BigQuerySource.
> Ref: 
> [https://stackoverflow.com/questions/60146887/expected-eta-to-avail-pipeline-i-o-and-runtime-parameters-in-apache-beam-gcp-dat/60170614?noredirect=1#comment106464448_60170614]



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

Reply via email to