Provides compiled expressions.
Provides implementation classes for compiled expressions.
Contains a workbench written in Swing for designing Mondrian schemas.
Utilities for internationalization and localization.
Defines a parse tree for MDX expressions.
Mondrian's core package, this defines connections and the catalog metamodel, and allows you to execute queries.
Defines the set of MDX built-in functions.
Defines MDX extension functions.
Implements the set of functions defined by the Visual Basic for Applications (VBA) specification.
Type system for MDX expessions.
olap4j driver for the Mondrian OLAP engine.
Provides a set a classes for logging the process of a task.
Implements the data access layer for the olap package.
Manages a cache of aggregates containing cell values.
Defines a 'matcher' which scans the schema to find candidate aggregate tables.
Provides primitives for policy-based caching.
Database-independent library for generating SQL.
Augments the Mondrian engine with server functionality.
Contains the server-provider interfaces (SPIs) which user-defined extensions to Mondrian should implement.
Provides implementations of SPIs defined in the
Suite of regression tests.
Regression tests relating to the build process.
Utilities for comparison-based testing.
Utilities to load test data.
Text user interface for Mondrian.
Provides a tag library for embedding MDX queries in JSP pages.
Implements the XML for Analysis API.
It is represented as an XML file. The metadata is loaded into memory the
first time you reference a dimensional model. You can modify the model at
runtime by creating instances of classes such as
todo: How members are calculated...
todo: How aggregations are batched...
todo: MDX functions. See user-defined functions.
Aggregations are based upon the relational model: as far as the aggregation
manager is concerned, there is no relationship between the columns
state. This means that all roll-ups are the same: you just drop
a column. Consider the 3 roll-ups possible by dropping a column from the
gender is equivalent to removing the
city is equivalent to rolling up to a higher
level in the
[Geography] hierarchy; and dropping
is not even allowed in the dimensional model (no, sorry, you can't ask about
products sold in a cities called 'Portland'). This approach will also allow us
to implement 'drill anywhere'.
An aggregation is defined by a search condition, for example,
('CA', 'OR', 'WA'), city = any, gender = 'M', measure = 'Unit sales'}.
any value is important; if we had asked for a specific
set of cities, we would not later be able to roll-up by dropping the
The caching strategy is to throw out the aggregation with the lowest cost/benefit ratio. The 'benefit' of an item is the effort it took to produce (effort which it is saving future queries) multiplied by its 'usefulness' which declines exponentially if it is not used over time. The 'cost' of an item is its size.