[net] TParallelMergingFile: don't rely on nbytes for UploadAndReset() #20211
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `nbytes` value returned by TDirectoryFile::Write() is only > 0 if we write at least one TObject to the file, which is not the case for non-TObject-based objects that handle their own writing (e.g. RNTuple through RMiniFile). This means that if we write only non-TObjects in a TParallelMergingFile we will never call UploadAndReset() by only checking nbytes. With this PR, we instead use GetBytesWritten() to check if anything gets written by TDirectoryFile::Write(), which works even in case of non- TObjects.
silverweed
requested review from
enirolf,
hahnjo,
jblomer,
pcanal and
vepadulano
Test Results 21 files 21 suites 3d 10h 25m 16s ⏱️ Results for commit 9194c07. |
jblomer
reviewed
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The
nbytesvalue returned by TDirectoryFile::Write() is only > 0 if we write at least one TObject to the file, which is not the case for non-TObject-based objects that handle their own writing (e.g. RNTuple through RMiniFile).This means that if we write only non-TObjects in a TParallelMergingFile we will never call UploadAndReset() by only checking nbytes. With this PR, we instead use GetBytesWritten() to check if anything gets written by TDirectoryFile::Write(), which works even in case of non- TObjects.
cc @amete - this should fix one of the issues you observed with your parallel file merger when you only merge RNTuples.