CDAP 6.8.0 - Trigger with Payload configuration fails to pass runtime arguments to the downstream pipeline
Description
CDAP 6.8.0
Precondition: Two deployed pipelines
Steps:
Configure an Inbound trigger in the downstream pipeline with Payload configuration > Runtime arguments
Run the upstream pipeline
Wait for the downstream pipeline to be triggered
Verify the runtime arguments values in the downstream pipeline
Expected: Downstream pipeline should get the runtime arguments from the upstream pipeline
Actual: Downstream pipeline fails with the error for the runtime argument not being defined
Release Notes
Fixed an issue that caused pipelines with triggers with runtime arguments to fail after the instance was upgraded to CDAP 6.8+ and 6.9.0.
Activity
Show:
De Lan April 17, 2023 at 4:17 PM
Hi It will be in 6.8.3 and 6.9.1. Correct me if I am wrong
Poojan Trivedi April 17, 2023 at 10:45 AM
Thanks .
Can you please let us know when this fix will be available to us, if you can.
De Lan April 13, 2023 at 1:26 AM
fyi, fix PR opened:
Poojan Trivedi April 12, 2023 at 4:10 PM
Hi , I tested with both the types (AND/OR) of triggers.
The trigger condition that I was using was: 'succeeds'.
De Lan April 12, 2023 at 4:00 PM
Hi , could you please also specify which type(AND/OR) of triggers you created using the two deployed pipelines and what’s the trigger condition(succeeds, stops, fails) for each triggering pipeline? Thanks!
Fixed
Pinned fields
Click on the next to a field label to start pinning.
CDAP 6.8.0
Precondition: Two deployed pipelines
Steps:
Configure an Inbound trigger in the downstream pipeline with Payload configuration > Runtime arguments
Run the upstream pipeline
Wait for the downstream pipeline to be triggered
Verify the runtime arguments values in the downstream pipeline
Expected: Downstream pipeline should get the runtime arguments from the upstream pipeline
Actual: Downstream pipeline fails with the error for the runtime argument not being defined