-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[do not merge] RNTuple Attributes prototype #19153
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
base: master
Are you sure you want to change the base?
Conversation
Test Results 20 files 20 suites 3d 7h 1m 24s ⏱️ For more details on these failures, see this check. Results for commit 95e7500. ♻️ This comment has been updated with latest results. |
This currently only works for a subset of cases, namely if all RNTuples have the same set of Attribute Sets.
Otherwise the build fails on some platforms due to unordered_map requiring a complete type for the value type
The payload of each list element is a Locator pointing to the Attribute RNTuple's Anchor followed by a string | ||
containing the Attribute Set's name. |
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.
The locator and the name should be in a record frame, so that we can extend it in the future.
This Pull request:
Draft PR for the RNTuple Attributes prototype.
This prototype allows writing, reading and merging TFile-based RNTuples containing Attributes. Note that the implementation is not final and cuts several corners in order to provide a proof of concept.
Note that this new optional feature requires the Binary Format to be bumped by one minor version.