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

Unable to guess schema - improve workflow and exception throwing/handling

Apply templateInsert Lucidchart DiagramXMLWordPrintable

    • Hide
      1. Change UIService.java (connectors-se/http-common/src/main/java/org/talend/components/http/service/) in the a little bit to enable the testing of EXECUTE_MOCK_JOB like this.
      2. Build the http-studio.car with the above change and deploy it to Studio.
      3. Run the job given in the Step 2 of TDI-T6019 (1.0)  to reproduce the problem
      Show
      Change UIService.java (connectors-se/http-common/src/main/java/org/talend/components/http/service/) in the a little bit to enable the testing of EXECUTE_MOCK_JOB like this. Build the http-studio.car with the above change and deploy it to Studio. Run the job given in the Step 2 of  TDI-T6019 (1.0)  to reproduce the problem
    • All
    • Small

      Unable to guess schema of HTTPClient working in the start node if we enable DiscoverSchemaException, which breaks TCOMP-2342.

      Guess the schema for the Processor doesn't work when it has an additional sub job with an Input component in it.
      For example we have subjob 1 and subjob 2.
      When we have only subjob 1, the guess schema for Output (processor) component works well.

      Throws an exception in common if the connection is really unavailable to guess schema

        1. couchbase-guess-error.png
          couchbase-guess-error.png
          124 kB
        2. image-2024-06-28-11-12-52-771.png
          image-2024-06-28-11-12-52-771.png
          27 kB
        3. image-2024-06-28-11-12-59-595.png
          image-2024-06-28-11-12-59-595.png
          29 kB

            emmanuel_g emmanuel gallois
            wyuan Wei Yuan
            emmanuel gallois, Wei Yuan
            Wei Yuan Wei Yuan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: