Uploaded image for project: 'Pentaho Data Integration - Kettle'
  1. Pentaho Data Integration - Kettle
  2. PDI-12719

Table Input step: add step error handling (was: Database steps: Return DB status message)



    • Type: Improvement
    • Status: Open
    • Severity: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Not Planned
    • Component/s: Step
    • Labels:
    • PDI Sub-component:
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.


      Table Input step: add step error handling

      Use case (see also the comments below):
      I am making use of the Table Output and Update steps in my Sparkl plugin. I'd like to provide the end-user the exact DB error message in case something goes wrong.
      So in general, I'd like to get hold of the DB status message. This could be implemented as an optional output of Kettle DB steps.

      Additional Use Case:

      I am using a Kettle transformation with a Table Input step to connect to a Redshift DB. I'm calling the transformation from a CTools CDF component via a CDA request.
      If the transformation fails due to a timeout in the Table Input step, the CDF component fails and displays an error that says "Error processing component (component_name)".
      If the transformation fails due to some other SQL error in the Table Input step, the CDA query returns a 501 because there's no way to handle the SQL error within the transformation.
      In both cases, but especially the one related to timeout, feedback about the error is missing because there's no Error Handling hop on the Table Input step.

        PractiTest Integration


            Issue Links



                Unassigned Unassigned
                diddy Diethard Steiner
                5 Vote for this issue
                5 Start watching this issue