fix: correct LZ0 to LZO in compression options#995
Merged
timsaucer merged 7 commits intoapache:mainfrom Jan 14, 2025
Merged
Conversation
Contributor
Author
|
Encountered weird CI build error This PR does not include Does anyone know how to solve this CI issue? |
kylebarron
reviewed
Jan 13, 2025
kylebarron
approved these changes
Jan 13, 2025
Contributor
Author
|
Encountered weird CI build error I reproduced this ruff error by changing my python venv from 3.10 to 3.12. Then I ran |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #979.
Rationale for this change
Correct confusion of lz0 for lzo
What changes are included in this PR?
lz0 -> lzo
Are there any user-facing changes?
Yes.
lzois not a valid compression method until it is implemented in arrow-rs.apache/arrow-rs#6970