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
There is no auto refresh or alerting feature when there is any change in the static schema definition, we can only identify this when a job fails due to schema mismatch. We need to populate the change by manually opening each action which used that schema and select the schema name again from the dropdown. In talend, there is an option to propagate the schema changes to all related jobs once it is changed. This will be particularly useful when the same schema is being used under multiple jobs.
There is no option to segregate the schema definitions under relevant sub folders for ease of use. I have tried placing the schema definitions under sub folders inside config\projects\default\metadata\schema-definition , but after placing them in folders, the schemas are not getting listed in the drop down for usage. This will be helpful to easily fetch the schema names from a huge list while selecting inside actions.
Upon choosing the static schema inside Text file input or output actions, it automatically populates currency as the system default currency symbol, though we are not setting any currency inside static schema configuration.
Issue Priority
Priority: 3
Issue Component
Component: Metadata, Component: Transforms
The text was updated successfully, but these errors were encountered:
What would you like to happen?
There is no auto refresh or alerting feature when there is any change in the static schema definition, we can only identify this when a job fails due to schema mismatch. We need to populate the change by manually opening each action which used that schema and select the schema name again from the dropdown. In talend, there is an option to propagate the schema changes to all related jobs once it is changed. This will be particularly useful when the same schema is being used under multiple jobs.
There is no option to segregate the schema definitions under relevant sub folders for ease of use. I have tried placing the schema definitions under sub folders inside config\projects\default\metadata\schema-definition , but after placing them in folders, the schemas are not getting listed in the drop down for usage. This will be helpful to easily fetch the schema names from a huge list while selecting inside actions.
Upon choosing the static schema inside Text file input or output actions, it automatically populates currency as the system default currency symbol, though we are not setting any currency inside static schema configuration.
Issue Priority
Priority: 3
Issue Component
Component: Metadata, Component: Transforms
The text was updated successfully, but these errors were encountered: