[
https://issues.apache.org/jira/browse/BEAM-4176?focusedWorklogId=126223&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-126223
]
ASF GitHub Bot logged work on BEAM-4176:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/18 18:45
Start Date: 23/Jul/18 18:45
Worklog Time Spent: 10m
Work Description: ryan-williams commented on issue #5935: [BEAM-4176]
Initial implementation for running portable runner tests
URL: https://github.com/apache/beam/pull/5935#issuecomment-407161088
I don't have comments on this change yet, but wanted to just mention [this
prototype](https://github.com/apache/beam/commit/b78f76f89f560406889dfa9c741e34d58bb05b7e)
of an ArtifactStagingService that:
- detects artifacts that have already been uploaded (by MD5)
- closes the connection to prevent redundant artifacts from being uploaded
- leaves the manifest with all the entries for each job (just with URIs that
may point to where a previous job staged the artifact)
It doesn't help the main pain point here (re-staging ~200MB of artifacts for
each test case) because it doesn't work across artifact-server instances, but
that's the next extension I'm planning to look into.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 126223)
Time Spent: 2h 50m (was: 2h 40m)
> Java: Portable batch runner passes all ValidatesRunner tests that
> non-portable runner passes
> --------------------------------------------------------------------------------------------
>
> Key: BEAM-4176
> URL: https://issues.apache.org/jira/browse/BEAM-4176
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Ben Sidhom
> Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> We need this as a sanity check that runner execution is correct.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
