TABLE w/ MERGE and computed group-by doesn't DISTRIBUTED MERGE
Description
Conclusion
None
Activity
Show:
Gavin Halliday June 15, 2018 at 10:39 AM
more: Something to do with sort(ds, a+b) being optimized to sort(ds, a, b)
Gavin Halliday June 15, 2018 at 10:33 AM
This is a great bug (yuk)! I'm not 100% sure of the cause, but it is something to do with the sort order not being tracked through an aggregate.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Created June 14, 2018 at 12:21 PM
Updated June 22, 2018 at 11:44 AM
Resolved June 22, 2018 at 11:44 AM
If MERGE option on TABLE and group-by field is computed, it appears the DISTRIBUTE MERGE is generated without the fieldvalue parameter for the MERGE option in DISTRIBUTE and shows as HASH DISTRIBUTE.
DISTRIBUTE(HASH32(_unnamed_1, internal), merge));
versus this when using a discrete field:
DISTRIBUTE(HASH32(fieldvalue, internal), merge*(fieldvalue)*);
The resulting aggregation is incorrect, not consolidated as expected.