Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Cassandra Scripted Data Source (BIRT)"
| Line 6: | Line 6: | ||
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 [https://github.com/hector-client/hector/downloads here]. | 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 [https://github.com/hector-client/hector/downloads here]. | ||
== Copying the Hector client library JAR files for use with BIRT Designer == | == 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 the Cassandra Scripted Data Source in the New Data Source wizard: | + | 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 the Cassandra Scripted Data Source in the New Data Source wizard:<br> |
Unable to find Hector client library jars to support Cassandra Scripted Data Source | 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 == | == 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. There is a known issue unrelated to Cassandra scripted data sources that may cause a ClassNotFound exception. Copy the commons-logging-api-1.1.1.jar to the birt/WEB-INF/lib/ folder resolve this problem.<br> | 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. There is a known issue unrelated to Cassandra scripted data sources that may cause a ClassNotFound exception. Copy the commons-logging-api-1.1.1.jar to the birt/WEB-INF/lib/ folder resolve this problem.<br> | ||
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.<br> | 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.<br> | ||
| − | If you do not copy the JAR files, the following error message appears at runtime: | + | If you do not copy the JAR files, the following error message appears at runtime:<br> |
Caused by: org.eclipse.birt.core.exception.CoreException: Error evaluating Javascript expression. Script engine error | Caused by: org.eclipse.birt.core.exception.CoreException: Error evaluating Javascript expression. Script engine error | ||
[[Category:BIRT]] | [[Category:BIRT]] | ||
[[Category:BIRT Example]] | [[Category:BIRT Example]] | ||
[[Category:BIRT Example Report]] | [[Category:BIRT Example Report]] | ||
Revision as of 15:51, 8 February 2013
< 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 the 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. There is a known issue unrelated to Cassandra scripted data sources that may cause a ClassNotFound exception. Copy the commons-logging-api-1.1.1.jar to the birt/WEB-INF/lib/ folder resolve this problem.
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