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

Make sure Salesforce runtime classes don't try to serialize RuntimeContainer from driver node

Apply templateInsert Lucidchart Diagram
    XMLWordPrintable

Details

    • Bug
    • Resolution: Is not a Bug
    • Major
    • None
    • None
    • None
    • None
    • All
    • Hide

      The RuntimeContainer is not designed to be serialized ever. It's always the holder of the local environment (on driver or worker node).

      There is probably a related issue of how to inject the RuntimeContainer pointer into a distributed component in a worker node, which depends on which methods of Source/Sink are called on driver or worker.

      See TCOMP-475

      Show
      The RuntimeContainer is not designed to be serialized ever. It's always the holder of the local environment (on driver or worker node). There is probably a related issue of how to inject the RuntimeContainer pointer into a distributed component in a worker node, which depends on which methods of Source/Sink are called on driver or worker. See TCOMP-475
    • Small

    Description

      Make sure Salesforce runtime classes don't try to serialize RuntimeContainer from driver node.
      They may use RuntimeContainer provided by worker nodes. There is no API, which allows to pass RuntimeContainer to driver node in Runtime classes. However we can add it if we need

      Attachments

        Activity

          People

            Unassigned Unassigned
            igonchar Ivan Gonchar
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: