ASF GitHub Bot logged work on BEAM-8889:

                Author: ASF GitHub Bot
            Created on: 21/May/20 22:42
            Start Date: 21/May/20 22:42
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on pull request #11778:
URL: https://github.com/apache/beam/pull/11778#issuecomment-632382830

   Run Python PreCommit

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:

Issue Time Tracking

            Worklog Id:     (was: 436250)
    Remaining Estimate: 130h 40m  (was: 130h 50m)
            Time Spent: 37h 20m  (was: 37h 10m)

> Make GcsUtil use GoogleCloudStorage
> -----------------------------------
>                 Key: BEAM-8889
>                 URL: https://issues.apache.org/jira/browse/BEAM-8889
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp
>    Affects Versions: 2.16.0
>            Reporter: Esun Kim
>            Assignee: VASU NORI
>            Priority: P2
>              Labels: gcs
>             Fix For: 2.22.0
>   Original Estimate: 168h
>          Time Spent: 37h 20m
>  Remaining Estimate: 130h 40m
> [GcsUtil|https://github.com/apache/beam/blob/master/sdks/java/extensions/google-cloud-platform-core/src/main/java/org/apache/beam/sdk/extensions/gcp/util/GcsUtil.java]
>  is a primary class to access Google Cloud Storage on Apache Beam. Current 
> implementation directly creates GoogleCloudStorageReadChannel and 
> GoogleCloudStorageWriteChannel by itself to read and write GCS data rather 
> than using 
> [GoogleCloudStorage|https://github.com/GoogleCloudPlatform/bigdata-interop/blob/master/gcsio/src/main/java/com/google/cloud/hadoop/gcsio/GoogleCloudStorage.java]
>  which is an abstract class providing basic IO capability which eventually 
> creates channel objects. This request is about updating GcsUtil to use 
> GoogleCloudStorage to create read and write channel, which is expected 
> flexible because it can easily pick up the new change; e.g. new channel 
> implementation using new protocol without code change.

This message was sent by Atlassian Jira

Reply via email to