You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you decide to rename a field, even when renaming it in the transform that generates it / puts it into the stream, the subsequent transforms that use it still reference it with the old name, which makes the pipeline fail.
It would be extremely practical to be able to rename stream-fields and automatically update their usages in the subsequent transforms.
Example: select-values-basic.hpl in samples/transforms, open "Test Data", rename "id" to "id1" ==> the pipeline fails with
"Rename, reorder fields.0 - ERROR: Couldn't find field 'id' in row!"
Issue Priority
Priority: 3
Issue Component
Component: Pipelines, Component: Hop Gui
The text was updated successfully, but these errors were encountered:
gmitter-ef
changed the title
[Feature Request]: update field in all transforms upon renaming
[Feature Request]: Update field in all transforms upon renaming
Feb 7, 2025
What would you like to happen?
When you decide to rename a field, even when renaming it in the transform that generates it / puts it into the stream, the subsequent transforms that use it still reference it with the old name, which makes the pipeline fail.
It would be extremely practical to be able to rename stream-fields and automatically update their usages in the subsequent transforms.
Example: select-values-basic.hpl in samples/transforms, open "Test Data", rename "id" to "id1" ==> the pipeline fails with
"Rename, reorder fields.0 - ERROR: Couldn't find field 'id' in row!"
Issue Priority
Priority: 3
Issue Component
Component: Pipelines, Component: Hop Gui
The text was updated successfully, but these errors were encountered: