Make the logging a bit more flexible in the case where we log java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler


Is there a way to avoid the below stack (even though it’s at the INFO level)? This is with SCC-assembly 2.5.1_2.11 against a DSE 6.8.3 cluster via Dataproc,



Pull Requests



Bret McGuire
September 22, 2020, 4:29 PM

Another approach to this ticket might be to allow a user to specify the type of JNI support they wish to use. This would address a problem that’s been raised on the Spark side re: the JNI dependency breaking the expectations of Spark packages. It would also address the underlying motivation for this ticket (since in the case cited by a user could specify “native Java” support and avoid the JNI checks all together), although admittedly it’s not a direct solution to this second point.

Bret McGuire
September 21, 2020, 8:33 PM as a possible fix at a logback level, but note that this wouldn’t work for other logging frameworks supported by slf4j. A code fix is probably the most robust answer here.




Madhavan Sridharan

Affects versions