beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-2264) Re-use credential instead of generating a new one one each GCS call
Date Fri, 23 Mar 2018 00:24:00 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 23/Mar/18 00:23
            Start Date: 23/Mar/18 00:23
    Worklog Time Spent: 10m 
      Work Description: charlesccychen commented on issue #4891: [BEAM-2264] Credentials were
not being reused between GCS calls
URL: https://github.com/apache/beam/pull/4891#issuecomment-375499986
 
 
   Thank you!  This is a great change.  LGTM.
   
   R: @aaltay for merge.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

    Worklog Id:     (was: 83401)
    Time Spent: 0.5h  (was: 20m)

> Re-use credential instead of generating a new one one each GCS call
> -------------------------------------------------------------------
>
>                 Key: BEAM-2264
>                 URL: https://issues.apache.org/jira/browse/BEAM-2264
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Luke Cwik
>            Assignee: Ahmet Altay
>            Priority: Minor
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We should cache the credential used within a Pipeline and re-use it instead of generating
a new one on each GCS call. When executing (against 2.0.0 RC2):
> {code}
> python -m apache_beam.examples.wordcount --input "gs://dataflow-samples/shakespeare/*"
--output local_counts
> {code}
> Note that we seemingly generate a new access token each time instead of when a refresh
is required.
> {code}
>   super(GcsIO, cls).__new__(cls, storage_client))
> INFO:root:Starting the size estimation of the input
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> INFO:oauth2client.client:Refreshing access_token
> INFO:root:Finished the size estimation of the input at 1 files. Estimation took 0.286200046539
seconds
> INFO:root:Running pipeline with DirectRunner.
> INFO:root:Starting the size estimation of the input
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> INFO:oauth2client.client:Refreshing access_token
> INFO:root:Finished the size estimation of the input at 43 files. Estimation took 0.205624818802
seconds
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> INFO:oauth2client.client:Refreshing access_token
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> INFO:oauth2client.client:Refreshing access_token
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> INFO:oauth2client.client:Refreshing access_token
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> INFO:oauth2client.client:Refreshing access_token
> INFO:oauth2client.transport:Attempting refresh to obtain initial access_token
> ... many more times ...
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message