Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Weird NORMALIZE behaviour with LOCAL and Inline Dataset

Environment

LnP Dev

Description

Not sure this is that big of an issue overall, but weird enough that I felt compelled to report it.  The use of LOCAL on NORMALIZE is allowed, but logically does not seem to have a lot of value in this case.  That said, the _myNames named output is coming out with 25 rows on a 25-way thor, as if the system copied it to every server on system.  Similar behavior is seen on other sized systems (i.e. 10 rows come out on a 10-way).

 Standalone code:

 

Let me know if you have questions or need explicit workunits or archives.

 

Conclusion

None

Activity

Show:

Gavin Halliday September 3, 2021 at 7:29 AM

It probably has to wait for the next minor release - because I don't want to break existing code.

Gavin Halliday September 3, 2021 at 7:28 AM

Yes, that looks like a bug. LOCAL should have no effect on NORMALIZE. What happens is the normalize gets combined with the inline dataset, and the local attribute is added to that combined operation. LOCAL on an inline dataset does have a meaning - duplicate this dataset on each node.
I should fix the bug, but also check if a warning is generate if LOCAL is specified when it has no meaning.

Joe Cella September 2, 2021 at 5:52 PM

Code for these two attributes (intended to read from the written dataset) should have been:

 

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Minor

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/15317

Affects versions

Created September 2, 2021 at 5:47 PM
Updated September 3, 2021 at 2:26 PM
Resolved September 3, 2021 at 2:26 PM