JasperSoft ETL Extended Big Data 6.0 Cassandra warning message

Issue Description

You have created a simple Cassandra Connection using your local Cassandra on your machine.

But it still gives you the following error message.

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Job MyJob ended at 09:22 17/10/2016. [exit code=0]?

Resolution

If you look at the log file you might see that the Cassandra job ran fine as it gave an exit code of 0.  The warning that you are getting about SLF4J defaulting to no-operation logger implementation is not because the component is not loading the SLF4J jar.  Here is the official explanation as of version 1.6,

http://www.slf4j.org/codes.html#StaticLoggerBinder

As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation.

If you are packaging an application and you do not care about logging, then placing slf4j-nop.jar in the class path of your application will get rid of this warning message. Note that embedded components such as libraries or frameworks should not declare a dependency on any SLF4J binding but only depend on slf4j-api. When a library declares a compile-time dependency on a SLF4J binding, it imposes that binding on the end-user, thus negating SLF4J's purpose.

If you want to make that warning not appear also notifying you of not being able to load that class since by default it will go to the NOP one, you can add via a tlibraryload the slf4j-nop.jar attached. Also see the attached test job.  It shows how the Cassandra components work. Now depending on your cassandra configuration you will have to make some changes to the job to adapt it to your environment.

Ref. Case 00071844

demo_cassandra.zip