[ https://issues.apache.org/jira/browse/BEAM-3371?focusedWorklogId=135732&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-135732 ]
ASF GitHub Bot logged work on BEAM-3371: ---------------------------------------- Author: ASF GitHub Bot Created on: 17/Aug/18 15:54 Start Date: 17/Aug/18 15:54 Worklog Time Spent: 10m Work Description: lgajowy edited a comment on issue #6244: [BEAM-3371] Enable running integration tests on Spark URL: https://github.com/apache/beam/pull/6244#issuecomment-413909472 BTW: what is the reason of the fact that filesToStage option is duplicated in `DataflowWorkerPoolOptions`, `FlinkPipelineOptions` and `SparkPipelineOptions`? Do you think we can move this to `PipelineOptions` interface? IMO it would make things even easier (maybe not only for this fix)? ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 135732) Time Spent: 0.5h (was: 20m) > Add ability to stage directories with compiled classes to Spark > --------------------------------------------------------------- > > Key: BEAM-3371 > URL: https://issues.apache.org/jira/browse/BEAM-3371 > Project: Beam > Issue Type: Sub-task > Components: runner-spark > Reporter: Lukasz Gajowy > Assignee: Jean-Baptiste Onofré > Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > This one is basically the same issue as > [this Flink's one|https://issues.apache.org/jira/browse/BEAM-3370], except > of two things: > - a detection of files to stage has to be provided in Spark, which is already > being developed [here|https://issues.apache.org/jira/browse/BEAM-981] > - the test execution is not interrupted by FileNotFoundException but by *the > effect* of the directory not being staged (absence of test classes on the > Spark's classpath, hence ClassNotFoundException). > Again, this probably could be resolved analogously as in flink, while > BEAM-981 issue is resolved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)