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

Stan Rosenberg commented on HADOOP-8528:
----------------------------------------

I am wrapping up an internal project which extends hadoop's snappy with

-- pure implementation (from org.iq80.snappy); selection is controlled via 
"io.compression.codec.snappy.decompressor.useNative" and 
"io.compression.codec.snappy.compressor.useNative"

-- (almost) full compliance with snappy's framing format 
(https://code.google.com/p/snappy/source/browse/trunk/framing_format.txt)

-- splittable format which doesn't require any external container format, e.g., 
sequencefile, or index file

I'd love to see it integrated into hadoop.  If there is interest, I'll link it 
to an upcoming github location. 
                
> Add pure java snappy as an option
> ---------------------------------
>
>                 Key: HADOOP-8528
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8528
>             Project: Hadoop Common
>          Issue Type: Wish
>            Reporter: Dave Revell
>            Priority: Minor
>
> Using native libs for snappy has some disadvantages:
>  - Requires libhadoop and libsnappy to be installed on servers, test 
> machines, and any server running a minicluster with a SNAPPY CF
>  - Requires configuration of java.library.path
>  - Complicates the POM
> A pure java implementation of snappy is available, ASL2 licensed:  
> https://github.com/dain/snappy .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to