[Mondrian] Mondrian Digest, Vol 102, Issue 2

Matt Campbell mcampbell at pentaho.com
Tue May 5 08:35:12 EDT 2015


Keep in mind that usage over Excel is not well tested or supported.  Focus on the MDX that is causing the segment load error.  It results in an IOOBE when determining types.  What's the datatype of the first level of the CUSTOMERNAME hierarchy?  If you just query for the members of that level w/o wrapping in AddCalculatedMembers do you see the same error?

Trying a few variations may help narrow down the issue.

------

select NON EMPTY Hierarchize(AddCalculatedMembers({DrilldownLevel({[CUSTOMERS.CUSTOMERNAME].[All CUSTOMERS.CUSTOMERNAMEs]})}))
  DIMENSION PROPERTIES PARENT_UNIQUE_NAME ON COLUMNS 
from [ImpalaDS]


Caused by: mondrian.olap.MondrianException: Mondrian Error:Internal error:
Error while loading segment; sql=[select sum(`ORDERFACT`.`ORDERLINENUMBER`)
as `m0` from `bigdata`.`ORDERFACT` `ORDERFACT`]
	at
mondrian.resource.MondrianResource$_Def0.ex(MondrianResource.java:977)
	at mondrian.olap.Util.newInternal(Util.java:2404)
	at mondrian.olap.Util.newError(Util.java:2420)
	at mondrian.rolap.SqlStatement.handle(SqlStatement.java:352)
	at mondrian.rolap.SqlStatement.execute(SqlStatement.java:252)
	at mondrian.rolap.RolapUtil.executeQuery(RolapUtil.java:350)
	at
mondrian.rolap.agg.SegmentLoader.createExecuteSql(SegmentLoader.java:625)
	... 8 more
Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
	at java.util.ArrayList.rangeCheck(Unknown Source)
	at java.util.ArrayList.get(Unknown Source)
	at mondrian.rolap.SqlStatement.guessTypes(SqlStatement.java:419)
	at mondrian.rolap.SqlStatement.execute(SqlStatement.java:241)
	... 10 more



-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On Behalf Of Murtaza Ghodawala
Sent: Tuesday, May 05, 2015 1:39 AM
To: mondrian at pentaho.org; greenlion at gmail.com; lucboudreau at gmail.com
Cc: 'Masiuddin Mohammed'
Subject: Re: [Mondrian] Mondrian Digest, Vol 102, Issue 2
Importance: High

Hi Luc,

I think we were not able to explain in detail. We get this issue in Pentaho 5.x BI EE Mondrian with IMPALA, only when we try to access this Mondrian OLAP Cube in Excel over XML/A interface. We do not get this issue if we access the Mondrian OLAP Cube in Pentaho User Console - Analysis report.
Does that mean Mondrian OLAP Cube is not being used in Pentaho User Console
- Analysis report and it only comes into picture when we access it from Excel? We are also using the latest Mondrian, IMPALA and Simba IMPALA drivers so there shouldn't be any issues related to old libraries.


Hi Justin,

Thanks for your observation at the generated MDX query, but when we execute this exact same query (with back quotes) in Cloudera IMAPAL query editor, it works absolutely fine and giving us correct result. Also as I mentioned in my email to Luc, we are having no problems in accessing this OLAP cube in Pentaho User Console - Analysis report. This issue only arises when we access this OLAP cube in Excel over XML/A interface.

Below is the exact query we executed in Cloudera IMAPAL query editor - 

select sum(`ORDERFACT`.`ORDERLINENUMBER`) as `m0` from `bigdata`.`ORDERFACT` `ORDERFACT`


Thanks and Regards,

Murtaza Ghodawala

Lead - Technology, R&D | eGroup
M.H. Alshaya Co. W.L.L.
Retail Division
P.O Box 181, Safat 13002, Kuwait
Phone: (+965) 2224 2063, Fax: (+965) 2224 2488, Mob: (+965) 97180549 www.alshaya.com

-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On Behalf Of mondrian-request at pentaho.org
Sent: Monday, May 04, 2015 7:00 PM
To: mondrian at pentaho.org
Subject: Mondrian Digest, Vol 102, Issue 2

Send Mondrian mailing list submissions to
	mondrian at pentaho.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.pentaho.org/mailman/listinfo/mondrian
or, via email, send a message with subject or body 'help' to
	mondrian-request at pentaho.org

You can reach the person managing the list at
	mondrian-owner at pentaho.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Mondrian digest..."


Today's Topics:

   1. Re: Mondrian Digest, Vol 101, Issue 8 (Justin Swanhart)
   2. Re: Mondrian Digest, Vol 101, Issue 8 (Luc Boudreau)
   3. Segment cache and multi-valued dimensions (Ricardo Fradinho)


----------------------------------------------------------------------

Message: 1
Date: Sun, 3 May 2015 10:57:47 -0700
From: Justin Swanhart <greenlion at gmail.com>
Subject: Re: [Mondrian] Mondrian Digest, Vol 101, Issue 8
To: Mondrian developer mailing list <mondrian at pentaho.org>
Cc: Masiuddin Mohammed <mohd.masiuddin at alshaya.com>
Message-ID: <CAA16EA9-F9AC-47AB-81FF-ABFFB0825E80 at gmail.com>
Content-Type: text/plain;	charset=us-ascii

Hi, 

In you error log the SQL appears to be using MySQL dialect (notice
backticks) sql=[select sum(`ORDERFACT`.`ORDERLINENUMBER`)
as `m0` from `bigdata`.`ORDERFACT` `ORDERFACT`]

I don't think Impala supports backtick identifiers (correct me if I'm wrong).  

I don't know how to fix it, but maybe this will point you in right direction.

--justin


Sent from my iPhone

> On May 3, 2015, at 3:38 AM, Murtaza Ghodawala
<murtaza.ghodawala at alshaya.com> wrote:
> 
> sql=[select sum(`ORDERFACT`.`ORDERLINENUMBER`)
> as `m0` from `bigdata`.`ORDERFACT` `ORDERFACT`]


------------------------------

Message: 2
Date: Mon, 4 May 2015 09:30:35 -0400
From: Luc Boudreau <lucboudreau at gmail.com>
Subject: Re: [Mondrian] Mondrian Digest, Vol 101, Issue 8
To: Mondrian developer mailing list <mondrian at pentaho.org>
Cc: Masiuddin Mohammed <mohd.masiuddin at alshaya.com>
Message-ID:
	<CAKTEAx9vTa0fKj3RKPW4=7TPF3rwZd93FR119g+W0b5hftq4jA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Murtaza,

The minimum required versions to use Mondrian and Impala are:

 - Mondrian 3.7.0+
 - Impala 1.3
 - Impala driver (OEM) 2.5.5.1007

Please be aware that these still have some limitations. They are documented here [1].

Cheers

Luc

[1]
http://wiki.pentaho.com/display/analysis/PA_CR_PA-3.7.0.0-752_impalad-1.3.0_
simba_JDBC4-2.5.5.1007
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.pentaho.org/pipermail/mondrian/attachments/20150504/cc17321b/at
tachment-0001.html 

------------------------------

Message: 3
Date: Mon, 4 May 2015 16:11:58 +0100
From: Ricardo Fradinho <ricardo.fradinho at webdetails.pt>
Subject: [Mondrian] Segment cache and multi-valued dimensions
To: Mondrian developer mailing list <mondrian at pentaho.org>
Message-ID:
	<CAJxMyGp8cGJ-HCAm6LN-3TWEp4TEV81NfJHvAHOd-FiHDesH6g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

I have a question around many to many / multi-valued dimensions support in
Mondrian:

Can I use Mondrian on top of a schema with 1:N relation on the fact => dimension without having the segment cache ?

Here's a simplified version of the model I'm looking at:

Fact books:

isbn        prints
----------- ------------
123-XYZ     1

Dimension book_authors:

isbn        author
----------- ------------
123-XYZ     Mr 001
123-XYZ     Mr 002
...
123-XYZ     Mr 010

I have a fact table that joins with a dimension that has several authors for the same book.
I want Mondrian to return sum(prints)=10 when I join the fact with the dimension table, but I want Mondrian to return sum(prints)=1 when don't query over the authors dimension, ie, just looking at the fact or another dimensions with a 1:1 relation.

If execute a query first with a authors breakdown and the information is stored in the segment cache, does Mondrian use that segment if I query a second time without the authors breakdown ?
If so, Mondrian will aggregate over the cached segment and sum(prints)=10.

Put differently, does Mondrian expect a 1:1 relation on the fact foreign key to dimension primary key ?

I'm not asking about the many to many feature support or semi/non additive measures, rather I'm looking at the consistency requirements when dealing with segment aggregates.


Thanks,
Ricardo Fradinho.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.pentaho.org/pipermail/mondrian/attachments/20150504/90787693/at
tachment-0001.html 

------------------------------

_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian


End of Mondrian Digest, Vol 102, Issue 2
****************************************

============================================================================================================================================
Alshaya Confidentiality Notice & Disclaimer This email and any attached or transmitted files may contain confidential and/or privileged information and are intended solely for the addressee(s) named. If you have received this information in error, please notify the sender by return email, do not redistribute this email message, delete it immediately and keep no copies of it.  All opinions expressed in this email are solely those of the author and do not necessarily represent those of Alshaya.  Neither this email nor any attached or transmitted files constitute a binding commitment on behalf of Alshaya.  Any purported commitment or purchase order is subject to final approval in accordance with our internal procedures and subject to contract in accordance with the relevant laws.  References to Alshaya include M.H. Alshaya Co. W.L.L. and all its affiliated companies.
_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian


More information about the Mondrian mailing list