Pentaho Reporting 3.9.1 released on SourceForge

Doug just uploaded the latest stable release of the Pentaho Report Designer on Sourceforge. Thanks Doug!

This is a bug-fix release addressing issues in the drill-linking editor and the formula-editor. It also enabled support for smarter Mondrian-Caching via the new ‘JDBCConnectionUUID’ property.

Be aware that using PRD-3.9.1 requires that you also use BI-Server 4.8. If you have an older BI-Server installation, you have to stick to the report-designer that came with it or upgrade your server to 4.8.

Thank you Sulaiman to handle the whole release process! Well done.

This entry was posted in Announcements, Release on by .
Thomas

About Thomas

After working as all-hands guy and lead developer on Pentaho Reporting for over an decade, I have learned a thing or two about report generation, layouting and general BI practices. I have witnessed the remarkable growth of Pentaho Reporting from a small niche product to a enterprise class Business Intelligence product. This blog documents my own perspective on Pentaho Reporting's development process and our our steps towards upcoming releases.

4 thoughts on “Pentaho Reporting 3.9.1 released on SourceForge

    1. ThomasThomas Post author

      No, Java and Visual Basic do not play together nicely. I would recommend a native component instead, even though they all seem to be commercial and expensive.

  1. liver diet

    hi, here is my situation
    i’m using pentaho open source ETL software to move common data source into the oracle

    but…
    – i got no access to mysql server
    – i only get mysql dump file
    – i want to move the data in dump file to the oracle 11g database
    – let say that the admin of mysql wont generate other data format like csv,etc

    what should i do then?… please advice

    thanks

    1. ThomasThomas Post author

      Simple: First, such questions get answered quicker on the Pentaho Kettle forum.

      One solution is to download a MySQL server to your local PC (its free anyway) and then to copy that dump into your local MySQL server. After that, use Kettles Database Input and Database Output step to copy the data from the running MySQL server to the Oracle server.

Comments are closed.