Expose the pointer for the LZ4 Compression buffer #485
Conversation
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
|
@alex-krash sorry for the ping. Any chance you pick up this contribution? Would help us to eliminate a manually patched jar, and potentially beneficial to others |
Contributor
Could you change target to develop? I can help to merge the PR and make it part of the upcoming 0.2.5 release. |
Contributor
Author
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Not sure if this is wanted / useful for others.
But in our case, we aren't using the full JDBC library, just this class to compress the
INSERTqueries (because we're doing some batching of records, then push as one batch to a HTTP output stream).Because of also other buffers, it is useful to know how much data is buffered into the LZ4 compression buffers, preventing having to call
flush()regularly.