Sort and apply attributes once per table partition #694
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #692
applysortandattrcall from inside the.replay.replaylogloop to immediately after it, so that sorting happens the minimal number of times (once per table partition) rather than once per log file..replay.pathlistdefinition from inside the loop to immediately before it, so it doesn't reset between log files. If TP logs are more granular than the HDB partition type (e.g. hourly vs daily) then.replay.pathlistwill have duplicate partition paths per table, butapplysortandattralready handles this by doingdistinct each pathlist.