Project: talenddataquality
Issue TDQ-8774: tMatchGroup component in map/reduce job is creating different GID than standard job
I have created a map/reduce job using tMatchGroup. The GID that is created has a different format than the GID from a standard job. GID from map/reduce job - d79469c1-c9fe-4de3-ac7c-e3190e3f5d6e GID from standard job - 1 I think these should be consistent and definitely prefer the GID from the standard job. TODO: Add a version to the component. if the component has no version defined (after an import action), then we output a numeric GID (for backward compatibility). if the component is just dragged&dropped on a new job, then the version is, let's say, 2. And the output GID is of string type. this means, nothing to change in the UI part.
Story points: 8