Uploaded image for project: 'Talend Component Kit'
  1. Talend Component Kit
  2. TCOMP-1411

ComponentManager relies on beam jar name. This is unlikely and should move to beam integration module.

Details

    • Work Item
    • Status: Done
    • Major
    • Resolution: Fixed
    • None
    • 1.1.9
    • None
    • All
    • GreenHopper Ranking:
      0|i1hh3v:
    • 9223372036854775807
    • Small

    Description

      We've hit the problem at this line again:

      https://github.com/Talend/component-runtime/blob/be039a5d961fb56fbe3136230c4fd5de2b70dbe5/component-runtime-manager/src/main/java/org/talend/sdk/component/runtime/manager/ComponentManager.java#L968

      In brief, to determine whether a class is one of the Beam core classes, it tests against the jar name. Unfortunately, Databricks renames jar files, and beam-sdks-java-core- becomes:

      /tmp/addedFile3061440985423865599dbfs__tpd_staging_datastreams_deps_org_apache_beam_beam_sdks_java_core_2_8_0_beam_sdks_java_core_2_8-d79c3.jar

      Both the prefix (addedFile3016....) and suffix (-d79c3.jar) can change between runs.

      Attachments

        Activity

          People

            rmannibucau Romain Manni-Bucau
            rskraba Ryan Skraba
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: