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
In Vortex we have an issue where FoR arrays might no longer be sorted after compression spiraldb/vortex#400. In vortex it makes sense to try to find a different compressor in cases where FoR encoding would overflow. We could consider doing the same here since those values will not bitpack well
The text was updated successfully, but these errors were encountered:
Everything can continue to behave as expected if the array after for encoding is converted to unsigned variant of the original type.
robert3005
changed the title
Consider restricting FoR encoding to arrays where it will not overflow subtraction
FoR encoding should convert to unsinged variant of the original type
Jun 21, 2024
In Vortex we have an issue where FoR arrays might no longer be sorted after compression spiraldb/vortex#400. In vortex it makes sense to try to find a different compressor in cases where FoR encoding would overflow. We could consider doing the same here since those values will not bitpack well
The text was updated successfully, but these errors were encountered: