Details
-
Bug
-
Status: closed
-
Minor
-
Resolution: Can't Fix
-
None
-
None
-
-
All
-
Description
If we change output schema from tMap component will generate new ChangeMetadataCommand to notice other external node this change.
But this Command contain two same schema between currentOutputMetadata and newOutputMetadata(ExternalNodeChangeCommand line:350).
So that other external node can not find this change by this command(for example tAdvancedFileOutputXML component).
Two parameter keep same schema is unuseful so that if we change currentOutputMetadata to be old one and keep newOutputMetadata as before, then we can avoid this issue.
After that create new external node will not need consider this issue again,just need the new external node implement metadataInputChanged method.
Attachments
Issue Links
- prerequisite of
-
TDQ-9487 change input columns' name, transfer changes to tMatchGroup, but when open the "Configuration wizard" still use the old name.
-
- closed
-