1 / 14

Mondrian stuff Julian Hyde - Mondrian founder & lead developer 3 rd Pentaho Community meetup Cascais September 25 t

Mondrian stuff Julian Hyde - Mondrian founder & lead developer 3 rd Pentaho Community meetup Cascais September 25 th 2010. What’s new. Analyzer Luc Boudreau olap4j 1.0 Mondrian 3.2 Mondrian 3.2.1 Mondrian 4.

charlee
Télécharger la présentation

Mondrian stuff Julian Hyde - Mondrian founder & lead developer 3 rd Pentaho Community meetup Cascais September 25 t

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mondrian stuffJulian Hyde - Mondrian founder & lead developer3rd Pentaho Community meetupCascaisSeptember 25th 2010

  2. What’s new • Analyzer • Luc Boudreau • olap4j 1.0 • Mondrian 3.2 • Mondrian 3.2.1 • Mondrian 4

  3. Select [Measures].[Unit Sales] on 0, [Time].[2010].Children on 1from [Sales]where [Time].[2010] Solution: attribute-oriented MDX: Select [Measures].[Unit Sales] on 0, [Time].[Time].[2010].Children on 1from [Sales]where [Time].[Year].[2010] Schema: <Cube> <Dimension> <Attribute> <Hierarchy> <Level source=a> <MeasureGroup> <Measure> <DimensionLink> <AggTable> Pedrinho’s problem

  4. Richer Semantic Model • Physical schema: • Only define attributes and relationships once • Compound keys • Attribute hierarchies • Hierarchies & attributes grouped into dimensions • E.g. Customers dimension contains Customer hierarchy (State-City-Customer) and Age, Gender, Salary attribute hierarchies

  5. Measure groups • In Mondrian 3.x, if you want a cube with multiple fact tables, you build a virtual cube: • <Cube name=“Sales”> <Table name=“sales_fact”/></Cube><Cube name=“Warehouse”> <Table name=“warehouse_fact”/></Cube><VirtualCube name=“Warehouse and Sales”> <Cube name=“Sales”/> <Cube name=“Warehouse”/></VirtualCube>

  6. Measure groups (2) • In Mondrian 4, cubes can contain multiple measure groups: • <Cube name=“Warehouse and Sales”> <MeasureGroups> <MeasureGroup name=“Sales”> <Table name=“sales_fact”/> <Measure name=“unit_sales”/> </MeasureGroup> <MeasureGroup name=“Warehouse”> <Table name=“warehousee_fact”/> <Measure name=“inventory_units”/> </MeasureGroup> </MeasureGroups></Cube> • Virtual cubes are obsolete(but still supported) • Many-to-many association betweenmeasure groups and dimensions • Different ways to link dimensions tofact tables

  7. Physical schema • <Schema> • <PhysicalSchema> • <Table> • <Column> • <CalculatedColumn> • <Key> • <Link> • <Cube> • <Dimension> • <Attribute> • <Hierarchy> • <Level> • <MeasureGroup> • <Measure> • <DimensionLink> • <AggTable>

  8. Schema validation • Mondrian 3 validation sucks • In mondrian 4, can validate at runtime or design time • Generate multiple warnings, errors • Each error has a location • Workbench should navigate to each error • Better validation in EE (!)

  9. Transition to mondrian 4.0 • Not easy… • Backwards compatible • Workbench functionality: • Upgrade workbench • OR… extend agile BI • OR… extend metadata editor • OR… • Community can help!

  10. Mondrian 4.0 summary • Attribute-oriented analysis • Physical model • Composite keys • Multiple fact tables • Virtual cubes obsolete • Better validation • Clean up of internals: • Make aggregate tables look like fact tables • Unify native SQL optimization, aggregate table usage, fact table selection • Transition will be hard… but worth it

  11. Questions?

  12. Thank you for attending!

More Related