Forum Discussion
16 Replies
- nganapathirajuFormer Employee
Did you look into Group By N with a setting of 0!! Try it and let us know.
- walkerline117Contributor
No, groupby N has limitation when using Ultra task.
So for us we are trying to build high performance API with Ultra task. GroupbyN can achieve the goal but as it can only work in Triggered/Schedule tasks.- nganapathirajuFormer Employee
Try moving that group by N to a child pipeline and see how it works for Ultra.
Most of the snaps (group by, group By N, aggregate snaps) work in child pipelines in Ultra mode as long as you return one document to the top level parent pipeline.
- thilkipNew Contributor
Can one of you let me know if there was a solution for this?
- heidi_andrewContributor
I have to do this a lot. The sql must have a way to match up on all of these. For example, one sql pulls the employee address. The dependent tables do not have an address on them so i have to put the employee's address on the dependent address rows matching on employee_id. I have a pipeline with 21 pipelines in it to get everything on one line. When you do this sort of pipeline, in the mapper, you will see inputs from both documents. For this file, i only want dependent records on my file but i want the input from the EE record to update the dependent's address fields. Those will show on the last mapper. bring in all of the Dependent fields but on the address fields, bring in the EE's address. These will show as Input_1_Address_line_1 for example.