Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-13562

[Playground] Support SCIO SDK

Details

    Description

      As a Beam Playground user, I want to get execution output for the specific SCIO example code that I run in Beam Playground

      Acceptance criteria:

      1. Beam SCIO example code executed on the backend
      2. Output received by the frontend
      3. Compilation failures are caught and redirected to the frontend app
      4. Runtime failures are caught and redirected to the frontend app

       

      Scenario: SCIO example code running

      Given: User ran valid Apache Beam Python example code in Beam Playground

      When: Backend accepts the gRPC request

      Then: Backend apply preparation steps for SCIO SDK

      AND: Backend apply validation steps for SCIO SDK

      AND: Backend compile scala code in jar file using sbt

      AND: Backend runs a new background process using the java console command to run jar file 

       

       __ 

      Given: Backend app runs jar file using java console command

      When: Code executed completely

      And: Stdout and stderr outputs located at local fs

      Then: Backend reads the stdout and sends its content to the frontend with complete message code

       __ 

      Given: Backend app runs jar file using java console command

      When: Code executed with error

      And: Stdout and stderr outputs located at local fs

      Then: Backend reads the stderr and sends its content to the frontend with an error message code

       __ 

      Given: Backend app runs executable file using java console command

      When: Execution is finished with any code

      And: Backend sent a response to frontend

      Then: Backend clean-ups build and runtime artifacts.

      Attachments

        Issue Links

          Activity

            People

              daria.malkova Daria Malkova
              IKozyrev Ilya Kozyrev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10h 20m
                  10h 20m