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 <[email protected]> wrote: > +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 > someone > > to deploy the speedup by just dropping in a single JAR into the class > path. > > > > That's what the xerial snappy jar does, actually. The native bits are all > in the jar file. > > -Dan >
