[ 
https://issues.apache.org/jira/browse/HADOOP-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053629#comment-13053629
 ] 

Taro L. Saito commented on HADOOP-7206:
---------------------------------------

@Scott

JNI interface is tightly coupled with the Java code, so splitting 
Java/JNI/native libraries would not work as you expected. A reasonable option I 
can think of is to provide snappy-java without native libraries. In this case, 
users need to compile/install snappy-java's native library (make install to 
copy libsnappy.so to /usr/local/lib) and a jar file without native libraries. 
This style fits to users who need to compile everything from scratch. 
Snappy-java tries to load native libraries in the path specified in 
java.library.path if no bundled native library is found. 

@Allen
I am not familiar with non-Sun JVMs, but loading .so files depends only on 
locally installed library (GLIBC 2.3 or higher). No other dependencies exists 
in pre-compiled native libraries (for Linix) in snappy-java, because I 
carefully chosen the compilation options to avoid extra dependencies. 


> Integrate Snappy compression
> ----------------------------
>
>                 Key: HADOOP-7206
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7206
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.21.0
>            Reporter: Eli Collins
>            Assignee: Alejandro Abdelnur
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-7206-002.patch, HADOOP-7206.patch, 
> v2-HADOOP-7206-snappy-codec-using-snappy-java.txt, 
> v3-HADOOP-7206-snappy-codec-using-snappy-java.txt, 
> v4-HADOOP-7206-snappy-codec-using-snappy-java.txt, 
> v5-HADOOP-7206-snappy-codec-using-snappy-java.txt
>
>
> Google release Zippy as an open source (APLv2) project called Snappy 
> (http://code.google.com/p/snappy). This tracks integrating it into Hadoop.
> {quote}
> Snappy is a compression/decompression library. It does not aim for maximum 
> compression, or compatibility with any other compression library; instead, it 
> aims for very high speeds and reasonable compression. For instance, compared 
> to the fastest mode of zlib, Snappy is an order of magnitude faster for most 
> inputs, but the resulting compressed files are anywhere from 20% to 100% 
> bigger. On a single core of a Core i7 processor in 64-bit mode, Snappy 
> compresses at about 250 MB/sec or more and decompresses at about 500 MB/sec 
> or more.
> {quote}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to