-
Notifications
You must be signed in to change notification settings - Fork 11
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
Implement LZ4 transport compression #33
Implement LZ4 transport compression #33
Conversation
If time permits, I'd like to solicit some feedback on this implementation. I can add more tests explicitly around reading/writing compressed blocks if desired. I stuck with @athre0z's sketch for As an aside, this is just one of the features that I wanted for my own use, but my current plans are to implement the DBInterface next. This will require something akin to #9. I also think we should maybe tear out the explicit query building on insert ( |
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.
Hi, thanks a lot for the PR!
I did a first quick pass and the overall implementation looks solid. I left a few comments and will do another reading pass later. It might make sense to move the CityHash128 implementation into a separate project / repository in order to allow other projects to use it as well, but I'd also okay with having it here for the time being.
We can move these discussions to issues but just wanted to jot down some thoughts.
Yes, I think that'd be best for readability!
Before:
After:
The other suggested changes were also implemented (thanks) |
@athre0z anything else you would like for this PR? |
Thanks for the update and your patience -- my time has unfortunately been rather limited in the past few days and will likely continue to be so for the next two weeks. I'll try to carve out some time tomorrow for a final review pass. In the mean time: I noticed that the |
No worries -- appreciate your thoughtful review! The comments you've made have been resolved. I will also see if I can squeeze a PR into
Resolved - unnecessary dep. |
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.
LGTM -- thank you for tackling this!
PR for #8. Opening here in case there are interim comments, suggestions, or requirements. I have seen the @athre0z branch and will incorporate as necessary. Plans are to finish remaining work as time permits.
CompressedBlock
or alternative refactoring