What would you like to happen?
Migration: https://issues.apache.org/jira/browse/HOP-3919
I've Defined a database connection with a name XXXX.
After that i made some pipelines.
After that i decided to change database name from XXXX to YYYY because of business decission.
All the pipelines i made keep the old name XXXX instead to update it to YYYY.
It would be great to relate the connection through an ID or update all the pipelines to the new name.
Discussion:
I agree on an option to find and replace occurrences.
I do not agree on adding an ID (well the name is the ID) generating ID's and attaching them to metadata objects would prevent you from creating a new connection that has to link to existing object in a different environment.
If you use the search perspective and search for the object name you can find all locations in the project where is is used.
you can then double click on the search line and it will jump you to the relevant transform
Issue Priority
Priority: 3
Issue Component
Component: Metadata
What would you like to happen?
Migration: https://issues.apache.org/jira/browse/HOP-3919
I've Defined a database connection with a name XXXX.
After that i made some pipelines.
After that i decided to change database name from XXXX to YYYY because of business decission.
All the pipelines i made keep the old name XXXX instead to update it to YYYY.
It would be great to relate the connection through an ID or update all the pipelines to the new name.
Discussion:
I agree on an option to find and replace occurrences.
I do not agree on adding an ID (well the name is the ID) generating ID's and attaching them to metadata objects would prevent you from creating a new connection that has to link to existing object in a different environment.
If you use the search perspective and search for the object name you can find all locations in the project where is is used.
you can then double click on the search line and it will jump you to the relevant transform
Issue Priority
Priority: 3
Issue Component
Component: Metadata