lz4-java

lz4-java copied to clipboard

Is there any demo for compress streaming data?

10

I have read this article https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md and it looks quite suitable for me to compress continous incoming data and append them into compressed local file. But unfortuanately I cannot found...

darouwan

Small improvement to LZ4BlockInputStream

1

While doing some testing I found a bug in my code that was related to how read byte[] will only return to the end of the current decompressed buffer. It...

oobles

StreamingXXHash issues

2

1) `StreamingXXHash32JNI` and `StreamingXXHash64JNI` should not override `finalize()`, it's bad for GC. Instead, they should use Cleaner. 2) They should support close() for explicit resource release. 3) The close() method...

leventov

issue 80: remove synchronization from isLoaded getter

1

noamBarkai

Clean up interfaces and deprecated methods

3

There are a number of interfaces: `LZ4Decompressor`, `LZ4Compressor`, `LZ4UnknownSizeDecompressor`. These all have abstract `compress`/`decompress` methods that are marked deprecated. Could this be cleaned-up? Shouldn't it be possible to just pass...

lJoublanc

Allow obtaining and restoring the streaming hashes' internal state.

1

This feature enables a "very large stream" hashing use case: Instead of trying to read a large remote object in a single pass, one can fetch chunks of it at...

rgallardo-netflix

Support for Memory classes in lz4-java

8

[Druid](http://druid.io/) is a open source datastore which uses Lz4-java for fast compression. We are moving our implementation from ByteBuffer to [Memory](https://github.com/DataSketches/memory) . Memory provides the following benefits over ByteBuffer -...

niketh

Optimised skip() method for LZ4BlockInputStream

2

If I only want to decompress some part of the file, let's say a section at the begining and some other bits at the end, I can use skip(). But...

panterose

Bad decompression performance on repeating data with short period (< 32)

2

I've studied the implementation of `wildIncrementalCopy` and found that it has a suboptimal approach to copying ranges which are close to each other (source and destination offset differ by 32...

mtopolnik

Idea to improve performance by eliminating one copying step

1

I'm going over your code while considering to use it for a Hazelcast enterprise feature. In the same effort I have done some I/O coding similar to the `write(byte[], int,...

mtopolnik