Replies: 2 comments 2 replies
-
Hi, put your data (Fake data transform) in the template pipeline (_inj-anti-normalizer.hpl) and use the parent ones (_test_inj-anti-normalizer.hpl) to inject the metadata only. |
Beta Was this translation helpful? Give feedback.
-
Update: I managed to get the "Anti-normalizer" transform as I wished, after struggling with a possible bug in Data grid and Metadata Injection transforms (check issue #4525 for details and workaround). You can find the result in the attached file below: you can import the files _inj-anti-normalizer.hpl and anti-normalizer.hpl in your projects, and use the latter one as a sub-pipeline with the Simple Mapping transform (check the file _test-anti-normalizer.hpl for the needed parameter specifications: grouping fields, key field name, value field name). Attached file: |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm posting here with an actual help request (such as those filed in the Hop mailing list... BTW, is it still active?).
I set up a simple "to be injected" pipeline with a Row Normalizer linked to a Dummy transform, the latter one is needed to forward data to the "injector" (parent) pipeline.
In the parent pipeline I generate some fake data to be streamed into the Row Normalizer, and use a static Data grid to specify the fields to normalize them. You can see both pipelines in the attached file below.
The pipeline isn't working as expected: I got the error
Unable to find field from upstream transform: FirstName
in the log, despiteFirstName
is specified both as a field name in the streamed data, and in the Data grid as field to normalize.Am I messing up something in the configuration, or is it a bug that needs to be reported as an issue?
Thanks in advance for your support.
[Next question: Why don't you use directly the Row Normalizer without injection? In the actual scenario I'm developing, I'm not aware of the metadata to be streamed, except for some fields that need to be present. So those data would be streamed into the Row Normalizer, and the field table would be injected by generating the field list with a Metadata structure of stream, after removing those I know are needed for "grouping". Hence, the name "Anti-normalizer" 😃 ]
Attached file:
anti-normalizer.zip
Beta Was this translation helpful? Give feedback.
All reactions