Wrangler Transform Recipe field should be hidden when SQL Precondition is selected
Description
Release Notes
Attachments
Activity
Avinash Achar April 3, 2023 at 2:55 PM
We will keep this behaviour for now. Need to figure out a better way to do this.
Arjan Bal April 3, 2023 at 4:59 AM
Got it. I think the UI should not send the fields that are disabled in the UI to the backend. I agree that making the backend ignore fields will lead to unexpected behaviour.
There can be situations in which its impossible for the backend to determine which fields need to be ignored since we don’t know which fields were visible in the UI widget and which were disabled and have values from the time they were enabled.
Fernando Velasquez March 31, 2023 at 5:27 PM
I think it makes sense to display this so the user is aware that there is a directive must be removed from the pipeline.
This way the directives will also be removed from the pipeline JSON, which can be quite confusing, as the directives will be in the JSON but not executed with the pipeline.
This works as I instructed Sagar to implement.
When SQL precondition is selected in Wrangler transform and a recipe field is added, validation fails with the message “Directives are not supported for precondition of type SQL”.
The widget could just hide the field to prevent users from entering a recipe instead of relying on backed to fail the validation.