Re: Snappy compressor (native->java)

+1 A problem with the native bits is this product feature only works on certain native platforms. On Mon, Jun 20, 2016 at 7:48 PM, Sai Boorlagadda wrote: > There were no problems on the JNI wrapper (with native bits) except that > maintaining native bits needs special development & testing effo

Re: Snappy compressor (native->java)

There were no problems on the JNI wrapper (with native bits) except that maintaining native bits needs special development & testing efforts than pure java one. On Mon, Jun 20, 2016 at 5:52 PM, Dan Smith wrote: > +0 If the native code is causing problems switching seems like a good > idea. > >

Re: Snappy compressor (native->java)

+0 If the native code is causing problems switching seems like a good idea. I would suggest looking into embedding the native bits into a JAR file. > There are some tricks you can do to write the native bits out to disk from > the JAR file to load them at runtime. This would make it easier for so

Re: Snappy compressor (native->java)

+1 pure java -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771 On Jun 20, 2016 4:58 PM, "Jacob Barrett" wrote: > +1 for pure java default and making the native a drop in option. > > I would suggest looking into embedding the native bits into a JAR file. > There are

Re: Snappy compressor (native->java)

+1 for pure java default and making the native a drop in option. I would suggest looking into embedding the native bits into a JAR file. There are some tricks you can do to write the native bits out to disk from the JAR file to load them at runtime. This would make it easier for someone to deploy

Snappy compressor (native->java)

Geode currently bundles xerial/snappy as a default implementation. And this is a "JNI wrapper" on google snappy implementation. "xerial/snappy" jar bundles several pre-compiled static libraries to support various OS (linux,