Large OLAP Hierarchies in Spotfire
When you are analyzing external cube data in Spotfire, you may encounter situations when a hierarchy filter takes a really long time to load, or even fails to load. This happens because the filter is populated in advance by reading the hierarchy outline from the cube. If the hierarchy is large (with many different levels and categories), the loading of all values at once may even cause problems for the cube data source itself.
If you notice that the creation of a filter takes an unreasonably long time, or, if you know that your cube contains a very large hierarchy, you can configure the hierarchy to be loaded on request in the filter, instead of loading the entire hierarchy at once.
- Configuring a Cube Hierarchy to be Loaded on Request
These steps describe how a cube hierarchy can be configured to be loaded on request, so that large OLAP hierarchies can be handled in Spotfire. - Hierarchy Filters Loaded on Request
When the connection has been configured to load values on request, the hierarchy filter will query the cube for the currently shown values only, and a new query is sent to the cube each time a new category is expanded.
- Configuring a Cube Hierarchy to be Loaded on Request
These steps describe how a cube hierarchy can be configured to be loaded on request, so that large OLAP hierarchies can be handled in Spotfire. - Hierarchy Filters Loaded on Request
When the connection has been configured to load values on request, the hierarchy filter will query the cube for the currently shown values only, and a new query is sent to the cube each time a new category is expanded.
Parent topic: Introduction