Update to Thriller MDX over JDBC driver
Update, October 2026: Thriller is now open source and runs over the Essbase REST API. The
thriller.print-tuple-member-separatelyandthriller.header-tuple-separatorhints below are no longer needed: each dimension on the rows is always its own column, and the members over a data column are joined with a space. See the announcement and the project page.
I made a few adjustments and fixes to the experimental Thriller MDX over JDBC driver I have been playing with off and on. As a quick recap, Thriller is a normal JDBC driver that essentially passes MDX queries straight through to an Essbase server, and then maps the results into a normal JDBC ResultSet using a set of provided “hints” that tell it how to make George Spofford cry flatten the results.
There were a couple of issues related to how queries with various CrossJoins were handled that should now be fixed. Additionally, there are now a couple of new options to provide more configurability over how tuples are split or joined together. Things are definitely getting interesting for this concept.