-
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
hadd writes files with unspecified compression algorithm #6616
Comments
Still present in current master. |
vepadulano
added a commit
that referenced
this issue
Mar 3, 2024
kristupaspranc
pushed a commit
to kristupaspranc/root
that referenced
this issue
Apr 10, 2024
lobis
pushed a commit
to lobis/root
that referenced
this issue
Apr 10, 2024
kristupaspranc
pushed a commit
to kristupaspranc/root
that referenced
this issue
May 21, 2024
silverweed
pushed a commit
to silverweed/root
that referenced
this issue
Aug 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The following sequence of commands shows how an output file f2.root produced via hadd has compression settings equal to 1, i.e. compression level is 1 but the compressoin algorithm is 0, which corresponds to RCompressionSetting::EAlgorithm::kUseGlobal. Unfortunately kUseGlobal does not correspond to a specific compression algorithm but it refers to the "compression setting for this process; may be affected by rootrc". In other words, a user that receives a file with compression algorithm 0 has no way to figure out what the compression algorithm actually is.
Expected behavior
The last command above should print full compression settings with non-zero compression algorithm, e.g.
101
.To Reproduce
I think any input file can be used to reproduce the problem, but e.g. this snippet produces a file
"f.root"
that can be used for the reproducer above:hadd f2.root f.root
then produces a filef2.root
with unspecified compression algorithm.The text was updated successfully, but these errors were encountered: