[prev in list] [next in list] [prev in thread] [next in thread] 

List:       avro-dev
Subject:    [jira] [Created] (AVRO-2781) org.xerial.snappy.SnappyError: .FAILED_TO_LOAD_NATIVE_LIBRARY. no nativ
From:       "Russell (Jira)" <jira () apache ! org>
Date:       2020-03-25 21:24:00
Message-ID: JIRA.13293935.1585171401000.127335.1585171440373 () Atlassian ! JIRA
[Download RAW message or body]

Russell created AVRO-2781:
-----------------------------

             Summary: org.xerial.snappy.SnappyError: .FAILED_TO_LOAD_NATIVE_LIBRARY. \
no native library is found for os.name=zOS and os.arch=s390x  Key: AVRO-2781
                 URL: https://issues.apache.org/jira/browse/AVRO-2781
             Project: Apache Avro
          Issue Type: New Feature
          Components: java
         Environment: os.name=zOS and os.arch=s390x
            Reporter: Russell


On architectures such as z/OS, where snappy c module does not exist, we get runtime \
failure:

org.xerial.snappy.SnappyError: .FAILED_TO_LOAD_NATIVE_LIBRARY. no native library is \
found for os.name=zOS and os.arch=s390x  
 It would be great if we had the option to get Avro to use the Java native snappy \
implementation instead of JNI, such as can be found here and used freely:  \
[https://github.com/dain/snappy]

This would resolve issues for all platforms which are currently unsupported.

Maybe an option to select native or JNI could be added into the snappy wrapper



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[prev in list] [next in list] [prev in thread] [next in thread]