You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes and no. One could print the clib version of, for example the first chunk. However, since when using append it is perfectly fine to use a different codec for different chunks, that might not be entirely reliable. One could also print the codec used in all chunks, but that would defeat the purpose of the info subcommand, which by design is meant to return quickly and read only the header of the file. Best solution would be to add a new field to the Bloscpack header, which can contain the clib int or -1 if it is non-uniform. The problem with that being, that of course the header definition must change and the code to handle this must be written. ;)
Ah yes, makes perfect sense. In fact, in the future it would be nice to add a special compression mode in Blosc (either c-blosc or python-blosc) so that a codec could be chosen automatically in order to optimize compression ratio, speed, or a balance between them.
So I agree that it makes non sense this to be supported at all, except for the case where the clib is enforced to be uniform.
Currently, the
info
subcommand does not offer info on the codec used for compressing a file:I think the recently added
get_clib(cbuffer)
function in python-blosc 1.2.1 should help here.The text was updated successfully, but these errors were encountered: