Hey David G,
Can you attach those to OFBIZ-641? I think they got lopped off the
mailing list.
Thanks!
--- David Garrett <[EMAIL PROTECTED]> wrote:
> Chris,
>
> Very nice work! Thanks for the effort.
>
> I have run into a problem and I am not sure if it is in your
> implementation
> or with Jpivot. I was hoping you could point me in the right
> direction.
>
> I have been able to reproduce my problem in the Foodmart example and
> have
> attached updated files, screen shots and error reports.
>
> The problem I have relates to the use of the "ordinalColumn" and the
> "nameColumn" attributes that can be used in a dimension. As you can
> see
> below, I have "enhanced" the Time dimension by adding the Day level
> plus
> added the ordinalColumn/nameColumn attributes.
>
> In the Warehouse cube...
> I can drill down to the month level BUT I can not drill down to day
> (mth-drill-fail.jpg). If the ordinalColumn/nameColumn attributes are
> removed
> I can drill down to the day level (mth-drill-ok.jpg).
>
> <Dimension name="Time" type="TimeDimension">
> <Hierarchy hasAll="false" primaryKey="time_id">
> <Table name="time_by_day"/>
> <Level name="Year" column="the_year" type="Numeric"
> uniqueMembers="true" levelType="TimeYears"/>
> <Level name="Quarter" column="quarter" uniqueMembers="false"
> levelType="TimeQuarters"/>
> <Level name="Month" column="month_of_year"
> uniqueMembers="false"
> type="Numeric" levelType="TimeMonths" ordinalColumn="month_of_year"
> nameColumn="the_month"/>
> <Level name="Day" column="day_of_month" uniqueMembers="false"
> type="Numeric" levelType="TimeDays"/>
> </Hierarchy>
> </Dimension>
>
> Do you have any suggestions as to what is going wrong?
>
> Thanks
> David G
>
>
> Notes:
> 1. The revised FoodMart.zip is attached.
> 2. Is there a simple solution to the drillPositionButton which is not
> displaying the correct string ... [EMAIL PROTECTED]
> 3. part of Error
> select {[Measures].[Store Invoice]} ON COLUMNS,
> {[Time].[1997].[Q1].[February]} ON ROWS
> from [Warehouse]
>
> [RolapSchemaReader]: 60: role: [EMAIL PROTECTED]
> [RolapSchemaReader]: 61: schema: [EMAIL PROTECTED]
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> Util.java:439:DEBUG] Util.lookupCompound: parent.name=Warehouse,
> category=unknown, names=[Measures].[Store Invoice]
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> RolapCube.java:1808:DEBUG] RolapCube.lookupChild: name=Warehouse,
> childname=Measures returning elementname=Measures
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> HierarchyBase.java:137:DEBUG] HierarchyBase.lookupChild:
> name=Measures,
> childname=Store Invoice returning elementname=Store Invoice
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> DimensionBase.java:126:DEBUG] DimensionBase.lookupChild:
> name=Measures,
> childname=Store Invoice returning elementname=Store Invoice
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> Util.java:493:DEBUG] Util.lookupCompound: found child.name=Store
> Invoice,
> child.class=mondrian.rolap.RolapStoredMeasure
> [RolapSchemaReader]: 60: role: [EMAIL PROTECTED]
> [RolapSchemaReader]: 61: schema: [EMAIL PROTECTED]
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> Util.java:439:DEBUG] Util.lookupCompound: parent.name=Warehouse,
> category=unknown, names=[Time].[1997].[Q1].[February]
> 2007-02-26 22:29:24,544 (http-0.0.0.0-8443-Processor4) [
> RolapCube.java:1808:DEBUG] RolapCube.lookupChild: name=Warehouse,
> childname=Time, status=hierUsage == shared returning elementname=Time
> 2007-02-26 22:29:24,554 (http-0.0.0.0-8443-Processor4) [
> HierarchyBase.java:137:DEBUG] HierarchyBase.lookupChild: name=Time,
> childname=1997 returning elementname=1997
> 2007-02-26 22:29:24,554 (http-0.0.0.0-8443-Processor4) [
> DimensionBase.java:126:DEBUG] DimensionBase.lookupChild: name=Time,
> childname=1997 returning elementname=1997
> 2007-02-26 22:29:24,554 (http-0.0.0.0-8443-Processor4) [
> RolapSchemaReader.java:238:DEBUG] looking for child "Q1" of
> [Time].[1997]
> 2007-02-26 22:29:24,554 (http-0.0.0.0-8443-Processor4) [
> RolapSchemaReader.java:238:DEBUG] looking for child "February" of
> [Time].[1997].[Q1]
> 2007-02-26 22:29:24,574 (http-0.0.0.0-8443-Processor4) [
> RolapSchemaReader.java:258:DEBUG] NumberFormatException in
> lookupMemberChildByName for parent = "[Time].[1997].[Q1]",
> childName="February", exception: For input string: "February"
> 2007-02-26 22:29:24,574 (http-0.0.0.0-8443-Processor4) [
> Util.java:474:DEBUG] Util.lookupCompound: parent.name=Q1 has no child
> with
> name=February
> 2007-02-26 22:29:24,574 (http-0.0.0.0-8443-Processor4) [
> Util.java:439:DEBUG] Util.lookupCompound: parent.name=Warehouse,
> category=member, names=[Time].[1997].[Q1]
>
>
>
>
> -----Original Message-----
> From: Chris Howe (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Monday, 19 February 2007 9:21 AM
> To: dev@ofbiz.apache.org
> Subject: [jira] Updated: (OFBIZ-641) Integrate Mondrian OLAP
>
>
> [
>
https://issues.apache.org/jira/browse/OFBIZ-641?page=com.atlassian.jira.plug
> in.system.issuetabpanels:all-tabpanel ]
>
> Chris Howe updated OFBIZ-641:
> -----------------------------
>
> Attachment: datawarehouse1.patch
>
> datawarehouse1.patch
>
> cleans up some superfluous Debug statements and makes it relative to
> datawarehouse.home
>
> > Integrate Mondrian OLAP
> > -----------------------
> >
> > Key: OFBIZ-641
> > URL:
> https://issues.apache.org/jira/browse/OFBIZ-641
> > Project: OFBiz (The Open for Business Project)
> > Issue Type: New Feature
> > Reporter: Chris Howe
> > Priority: Minor
> > Attachments: create-foodmart-mysql.zip,
> datawarehouse1.patch,
> > datawarehouse1.patch, freemrkrTransform.patch, screenshot-1.jpg,
> > screenshot-2.jpg
> >
> >
> > I'm currently working on integrating Mondrian OLAP using services
> and
> simple-methods. I plan on doing this in a simliar manner that the
> Trixbox
> (Asterisk) issue was done. I'm creating this issue now instead of
> when I
> have something to add for collaboration reasons and so that I can
> play with
> Mylar around this.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
