Showing posts with label pentaho. Show all posts
Showing posts with label pentaho. Show all posts

Tuesday, July 17, 2018

Cannot run Pentaho BI server on Mac

Leave a Comment

I've been trying to install Pentaho BI Server (Community Edition) on Mac but I did not manage to make it run:

Does anyone know a good matching between the Java version and Pentaho?

When I try to run pentaho-server-ce-8.0.0.0-28 there is an issue related with Dcatalina.endorsed deprecated in Java 8 that is preventing the virtual machine to start and for the newest one shows lot of errors.

Thank you.

1 Answers

Answers 1

I found this in the spoon.sh. If it doesn't help, maybe it explains...

echo "I'm sorry, this Mac platform [$ARCH] is not yet supported!"

echo "Please try starting using 'Data Integration 32-bit'

or" echo "'Data Integration 64-bit' as appropriate."

exit;

Read More

Wednesday, December 6, 2017

Metadata Business Layer as Searchable List of Datapoints

Leave a Comment

In the Pentaho User Console, when someone creates a new interactive report, they get the list of datapoints on the left side like this:

Pentaho Interactive Reports Data Fields

How can I query the Pentaho Metadata so that I can get this structure and set up a searchable list in it's own page?

I'm hoping that there is a useful class somewhere that will help me with getting this into a jsp...

0 Answers

Read More

Monday, April 18, 2016

MDX date range query with a missing boundry date

Leave a Comment

I need an MDX query for Mondrian filtered by date, where one or both of the boundry dates may not exist. I'm using the query below that works as long as both 2013-01-01 and 2013-01-08 dimensions exist. If one of the two dates does not exist then it returns no results, even though the dimensions in between do exist. How would I get this query to work even in the case of a missing boundry date dimension?

SELECT NON EMPTY {Hierarchize({[Measures].[Number of Something]})} ON COLUMNS, NON EMPTY {[Date].[2013-01-01]:[Date].[2013-01-08]} ON ROWS FROM [Users] 

3 Answers

Answers 1

MDX is built with the assumption that every member that you refer to exists; it is best then to make sure all conceivable date dimension members do exist by having a separate table with these values precomputed.

You could get tricky and implement that table as a stored procedure but date dimensions don't take up a lot of space in the grand scheme of things so you'd hardly ever do this.

I don't know of any other way to solve your problem.

Answers 2

try to eliminate the NON EMPTY

Answers 3

Even I haven't yet understand the reason of implementing this logic, you can hide this by adding . If you add custom member in Mondrian try it.

    /* Exclude Missing Member */ Create Set CurrentCube.[MissingMemberSet] As iif(IsError(StrToMember("[Dimension].[Hierarchy].&[MEMBER]")), {}, {[Dimension].[Hierarchy].&[MEMBER]});  Create Member CurrentCube.Measures.[Calculation on Missing Member] AS IIF ([MissingMemberSet].Count > 0, ([Dimension].[Hierarchy].&[MEMBER],Measures.[X Measure]), 0 ) , FORMAT_STRING = "Currency", LANGUAGE = 1033, NON_EMPTY_BEHAVIOR = { [X Measure] }, VISIBLE = 1 ,  DISPLAY_FOLDER = 'Display Folder'  ; 

Also you can implement in using IIF(IsError or IIF(Exists MDX functions.

Read More