[jira] [Work logged] (BEAM-9845) Stage dependencies over the expansion service.

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 01/May/20 01:30
            Start Date: 01/May/20 01:30
    Worklog Time Spent: 10m 
      Work Description: chamikaramj commented on a change in pull request #11557:
URL: https://github.com/apache/beam/pull/11557#discussion_r418376845



##########
File path: sdks/python/apache_beam/transforms/sql_test.py
##########
@@ -66,20 +66,8 @@ class SqlTransformTest(unittest.TestCase):
         --tests apache_beam.transforms.sql_test \\
         --test-pipeline-options="--runner=FlinkRunner"
   """
-  @staticmethod
-  def make_test_pipeline():
-    path_to_jar = subprocess_server.JavaJarServer.path_to_beam_jar(
-        ":sdks:java:extensions:sql:expansion-service:shadowJar")
-    test_pipeline = TestPipeline()
-    # TODO(BEAM-9238): Remove this when it's no longer needed for artifact
-    # staging.
-    test_pipeline.get_pipeline_options().view_as(DebugOptions).experiments = [
-        'jar_packages=' + path_to_jar

Review comment:
       Can we update 'validate_runner_xlang_test.py' for Spark and Flink as well or do we need additional changes before that.
   jar_packages cannot be completely removed yet since Dataflow needs it.

##########
File path: sdks/java/expansion-service/src/main/java/org/apache/beam/sdk/expansion/service/ExpansionService.java
##########
@@ -317,6 +321,14 @@ default InputT createInput(Pipeline p, Map<String, PCollection<?>> inputs) {
     Pipeline pipeline = Pipeline.create();
     ExperimentalOptions.addExperiment(
         pipeline.getOptions().as(ExperimentalOptions.class), "beam_fn_api");
+    List<String> classpathResources =
+        detectClassPathResourcesToStage(Environments.class.getClassLoader(), pipeline.getOptions());

Review comment:
       This assumes that the set of classpath resources required to execute Java SDK harness and execute the cross-langauge Java step to be the same as the set of classpath resources specified when starting up the expansion service, right ?
   
   I'm wondering if we can always rely on this. At least we should document this so that users are aware how to stage additional resources if needed.




----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 429315)
    Time Spent: 50m  (was: 40m)

> Stage dependencies over the expansion service.
> ----------------------------------------------
>
>                 Key: BEAM-9845
>                 URL: https://issues.apache.org/jira/browse/BEAM-9845
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core, sdk-py-core
>            Reporter: Robert Bradshaw
>            Assignee: Robert Bradshaw
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> This will obviate the need for jar_packages. 



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