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

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

                Author: ASF GitHub Bot
            Created on: 09/Sep/21 01:40
            Start Date: 09/Sep/21 01:40
    Worklog Time Spent: 10m 
      Work Description: meowcakes removed a comment on pull request #15461:
URL: https://github.com/apache/beam/pull/15461#issuecomment-915691931


   Run Java_Examples_Dataflow_Java11


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 648314)
    Time Spent: 3.5h  (was: 3h 20m)

> Spark JobServer should bundle AWS IO libraries to support staging on S3
> -----------------------------------------------------------------------
>
>                 Key: BEAM-12845
>                 URL: https://issues.apache.org/jira/browse/BEAM-12845
>             Project: Beam
>          Issue Type: Improvement
>          Components: jobserver
>    Affects Versions: 2.32.0
>            Reporter: Rogan Morrow
>            Priority: P2
>             Fix For: 2.33.0
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> The AWS filesystem libraries are not included in the Spark JobServer. These 
> are necessary to allow staging artifacts to S3.
> There is a TODO in the code to update the dependencies to support the AWS 
> filesystem.
> [https://github.com/apache/beam/blob/master/runners/spark/job-server/spark_job_server.gradle#L62]
> Additionally, the `amazon-web-services2` library is built without a 
> dependency on STS. A dependency on STS is needed to support authentication 
> from EKS with IAM roles for service accounts.



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

Reply via email to