Welcome to the Red Book for HPCC Systems® 6.4.x. There are several sections in this Red Book as follows:
...
- To raise an issue, use our Community Issue Tracker. Please create yourself an account if you don't already have one, to get automatic updates as your issue progresses through the workflow.
- To ask a developer a technical question about something you are doing or have encountered, post in the Developer Forum.To add a note into the RedBook, please contact Lorraine Chapman with full details.
General HPCC Systems Core Platform
...
6.4.6 requires the updating of all plugins
When updating the HPCC platform to 6.4.6, you must also update any plugins (such as WsSQL, Ganglia, or Nagios).
This is as a result of the following change made in the platform:
...
https://track.hpccsystems.com/browse/HPCC-17084
Inconsistent #stored/#constants are now caught and reported as errors
A warning (defaulting to error severity) has been added in 6.4.0 to catch these inconsistencies, which means that some queries will need fixing when migrated to 6.4.0. The correct fix is to only have a single #STORED or #CONSTANT for a single id.
...
to the query. However, while your query may still work as before, there is no guarantee which of the inconsistent values it will be using so it is recommended that you implement the correct fix as soon as possible.
https://track.hpccsystems.com/browse/HPCC-16684
...
https://track.hpccsystems.com/browse/HPCC-17659
Incorrect code generation on some aggregation operations on inline datasets
Previously, when an operation on an inline dataset (e.g. a filter) included a min/max (or other aggregate operation) of a filter/limit of the same dataset, the resulting values from the inline dataset were being incorrectly substituted into the min/max operation.
...
ds := inline-dataset child := limit(ds, 4); (a filter might also trigger it) m := max(child, some-field); output(ds(some-other-field != m));
This was incorrect behaviour which has now been corrected. Be aware that the behaviour of some existing queries that were relying on this incorrect behaviour, may now change.
https://track.hpccsystems.com/browse/HPCC-17652
...