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

Definition of an error contract to handle expected errors

Details

    • New Feature
    • Status: closed
    • Major
    • Resolution: Done
    • None
    • 1.1.22
    • None
    • All
    • GreenHopper Ranking:
      0|i1pkhv:
    • 9223372036854775807
    • Small

    Description

      In TDC team, we're facing an issue regarding error handling in tacokit forms, we don't have any way to differentiate a true connector exception (meaning there is a non-handled issue in the connector) and a simple user misconfiguration (e.g an incorrect filename using s3 connector).
      Any exception thrown while calling a trigger through tacokit will be translated to a http 500 error by the server, ending up displayed to the end user.

      Connectors could define a contract allowing to identify an expected exception.
      This contract could simply be to throw unexpected exception as usual (that would be like today, an OOM can be thrown) but wrap other results into an object which would either be a success(result) or a failure(error).
      Such a contract is already available for HealthCheck with the HealthCheckStatus that can either be OK or KO.

      Attachments

        Issue Links

          Activity

            People

              emmanuel_g emmanuel gallois
              tricquebourg Timothée Ricquebourg
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: