-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ntuple] Refactor RNTupleWriter into RNTupleFillContext #14391
Conversation
Starting build on |
Test Results 9 files 9 suites 1d 19h 5m 5s ⏱️ For more details on these failures, see this check. Results for commit c415866. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I guess as we move forward and support multiple contexts at the same time, we have to revisit some of the methods, e.g. who owns the sink and what GetNEntries()
should return.
A context is responsible for preparing a cluster, and will be the unit of parallelisation for concurrent writing.
This is not used yet (RNTupleWriter directly observes the sink's metrics to avoid an extra prefix), but will be useful for parallel writing with multiple contexts.
a080c9d
to
c415866
Compare
Starting build on |
A context is responsible for preparing a cluster, and will be the unit of parallelisation for concurrent writing. Also has a commit to return
const
reference fromRNTupleWriter::GetModel()
.