Skip to:

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

PARTITION key produces incorrect results (missing rows) if some parts of key had 0 records

Description

When a PARTITION key is built, if some parts had 0 rows, then the TLK is being built with fewer entries than the width of the key.
As a consequence some of the jhtree code for getPartition() incorrectly derives the target partition and causes Thor to send the requests to lookup on the wrong slaves/against the wrong parts.

Conclusion

None

Activity

Show:

Jacob Cobbett-Smith December 6, 2018 at 6:10 PM

NB: this was seen as an issue (mismatch) via regression query bug12130.ecl on a cluster with 5 slaves.

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

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

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

Affects versions

Created December 6, 2018 at 6:09 PM
Updated January 16, 2019 at 11:50 AM
Resolved December 7, 2018 at 4:43 PM

Flag notifications