Cassandra Scripted Data Source (BIRT)

< To: Report Developer Examples (BIRT)
BIRT 4.2.2 and later supports scripted data source connections for use with Cassandra distributions, including:

• Apache Cassandra
• Datastax Cassandra Community
• Datastax Cassandra Enterprise

BIRT connects to and queries a Cassandra data source using the Hector API. You must copy the Hector client library JAR files to the appropriate folders for both BIRT Designer and the BIRT runtime deployment application. You can download the JAR files from here.

Copying the Hector client library JAR files for use with BIRT Designer

Copy the JAR files to the org.eclipse.birt.me.prettyprint.hector_<version>/lib/ folder and restart BIRT Designer. If you do not copy the JAR files, the following error message appears when you select Cassandra Scripted Data Source in the New Data Source wizard:

Unable to find Hector client library jars to support Cassandra Scripted Data Source

Copying the Hector client library JAR files for use with a BIRT runtime deployment application

For OSGi BIRT runtime deployment, copy the JAR files to the org.eclipse.birt.me.prettyprint.hector_<version>/lib/ folder and restart the runtime deployment application. If the "Servlet ViewerServlet is not available" error message appears, copy the org.apache.commons.logging_<version>.jar (available in WEB-INF/platform/plugins/) to the birt/WEB-INF/lib/ folder. This is a known issue with tomcat-6 that is independent of Cassandra scripted data sources.
For non-OSGi BIRT runtime deployment, copy the JAR files to the <installation_folder>/webapps/birt_runtime/scriptlib/ folder and restart the runtime deployment application.
If you do not copy the JAR files, the following error message appears at runtime:

Caused by: org.eclipse.birt.core.exception.CoreException: Error evaluating Javascript expression. Script engine error