General Behavior

When enabled, performance profiling data is generated and recorded. The availability of this setting is controlled by your license.

The number of filter values that can be listed in an Ad Hoc view that is based on an OLAP schema. If your filters have a large number of possible values, use this setting to allow Jaspersoft OLAP to return them all. Note that setting this value to a large number can impact the performance of your OLAP.

Turns off caching completely. Disabling caching can have a very noticeable negative performance impact.

If disabled, Jaspersoft OLAP returns an exception if you attempt to drill-through. This can be useful when the underlying data contains confidential information or is so voluminous that drill-through performance would be unacceptable.

When tracing is enabled, Jaspersoft OLAP formats SQL queries in the trace output with line breaks, which makes them easier to read.

The maximum number of concurrent queries is allowed.

When set to a number greater than 0, result sets are limited to the specified number of rows.

For each Jaspersoft OLAP instance in your deployment, the maximum number of concurrent threads that can be used for MDX queries. For more information about running multiple instances in a single deployment, refer to Performance Tuning.

Specifies the interval between polling operations performed by the RolapConnection shepherd thread. This controls query timeouts and cancellation, so a small value (a few milliseconds) is usually best. When this is set to a value higher than the value defined for the If > 0, Maximum query time (number of seconds) setting, the timeout is not enforced as expected.

When evaluating an MDX query, the maximum number of passes is allowed. Jaspersoft OLAP returns an error when this threshold is exceeded; for example, the error may occur during complex calculations.

If entered, this must be a Java class name that is an implementation of the mondrian.calc.ExpCompiler interface. Refer to the Mondrian Javadoc for more information.

Specifies whether the MDX parser considers the case of identifiers.

When set to a number greater than zero, defines a limit on the number of cells that can be batched together when building segments.

Specifies whether siblings at the same level of a dimension are compared according to the order key value retrieved from their ordinal expression. By default, ordinal expressions are only used for ORDER BY, and Jaspersoft OLAP ignores the actual values. When this property is enabled, Jaspersoft OLAP can correctly order members when native filtering is used. Note that this setting requires that the RDBMS provides non-null instances of java.lang.Comparable that yield the correct ordering when calling their Comparable.compareTo method.

When set to a value greater than zero, Jaspersoft OLAP times out if the query takes longer than the specified number of seconds. If a query exceeds the limit, Jaspersoft OLAP returns an error.

For more information, refer to the Query Limit and Result Limit entries in this table.

This property determines how many members Mondrian reads in one block from the database. Setting large values for this property increases performance but can overload memory. Values should be prime with mondrian.result.limit.

For more information, refer to the configuration guide.

Performance tuning variable. This property only applies when SparseSegmentCountThreshold is enabled. It determines whether to use a sparse or a dense representation when collections of cell values are stored in memory.

Performance tuning variable. this property only applies when the SparseSegmentDensityThreshold is set. It determines whether a sparse or a dense representation is used when collections of cell values are stored in memory.

When storing collections of cell values, Jaspersoft OLAP can use either a sparse or a dense representation. This is determined by the possible and actual number of values: density is calculated as actual / possible.

Whenever possible, Jaspersoft OLAP uses a sparse representation - countThreshold * actual > densityThreshold.

For example, for the default values (countThreshold = 1000, SparseSegmentDensityThreshold = 0.5), Jaspersoft OLAP uses a dense representation for:

If there are fewer actual values or more possible values, Jaspersoft OLAP uses a sparse representation.

When enabled, Jaspersoft OLAP ignores invalid members during schema load. They are treated as null members if they are referenced in a later query.

When enabled, Jaspersoft OLAP ignores invalid members during query validation. Invalid members are ignored and are treated as null members.

Specifies how Jaspersoft OLAP should represent a null member in the result output.

When set to a number greater than 0, the maximum number of iterations allowed when evaluating an aggregate. When set to 0, iterations are unlimited.

If a query exceeds the limit, Jaspersoft OLAP returns an error that specifies this property’s value. For more information, refer to the Query Limit and Result Limit entries in this table.

When set to a number greater than 0, specifies a threshold for a crossjoin input list's size. If it exceeds this value, and the axis has the NON EMPTY qualifier, Jaspersoft OLAP uses the non-empty optimizer.

When this property is set to 0, Jaspersoft OLAP applies the non-empty optimizer to all crossjoin input lists. To ensure that the optimizer is never applied to crossjoin input lists, set this value to the Integer.MAX_VALUE.

When enabled (the default setting), segment data are rolled up in-memory.

When dimensions unrelated to a measure are detected during aggregation, the measure is ignored in the evaluation context. Note that this property can only affects measures whose CubeUsage’s IgnoreUnrelatedDimensions is false.

For more information, refer to the configuration guide.

Determines if elements of dimension (levels, hierarchies, and members) must be prefixed with the dimension name in MDX queries.

This property determines whether certain queries succeed or fail based on the way the dimension elements are defined in the MDX query. When this property is enabled, this query fails:

select {[Omaha]} on columns from cust

When this property is disabled, that same query succeeds.

With the property enabled, the correct query is:

select {[Nebraska].[Omaha]} on columns from cust

If your schema is very large or complex, Jaspersoft recommends enabling this setting, as processing such schemas can be very resource-intensive.

For more information, refer to the configuration guide.

By default, when Jaspersoft OLAP attempts to divide by zero or null, it evaluates to Infinity, which is correct for some analysis providers. When this property is enabled, Jaspersoft OLAP instead evaluates such calculations to null, which can be helpful in certain circumstances.

Comma-separated list of classes to use to get statistics about the number of rows in a table or the number of distinct values in a column.

Specifies how to evaluate the SOLVE_ORDER:

Aggregate Settings

When enabled, Jaspersoft OLAP identifies tables in the database that are aggregated, and uses those aggregate values. Those values may use a different aggregator than the measures in the OLAP schema. Users may expect to see the aggregate values as defined by the schema rather than those in aggregate tables. In this case, disable the Enable Aggregate Tables option.

For more information, refer to the configuration guide.

Performance tuning variable for aggregates. This property only applies when aggregate tables are used. Consider using this property when optimizing for tables with many large columns. this property determines whether aggregate tables are ordered by volume or row count.

When this property is enabled, Jaspersoft OLAP uses the aggregate table with the smallest volume (number of rows multiplied by number of columns); when it is disabled, Jaspersoft OLAP uses the aggregate table with the fewest rows.

Determines whether Jaspersoft OLAP optimizes predicates. When this property is enabled, Jaspersoft OLAP optimizes certain predicates.

When it is disabled, predicates are only optimized when all of a dimension’s members are included. In this case, Jaspersoft OLAP only retrieves the data specified in the query.

For more information, refer to the configuration guide.

Specifies a file that defines aggregate table recognition rules. This file can either reside in the application server or the file system. Typically, you can accept the default.

The AggRule element's tag value. Typically, you can accept the default.

Determines whether Jaspersoft OLAP prints the SQL code generated for aggregate tables.

When this property is enabled, Jaspersoft OLAP processes each aggregate request and prints both the lost and collapsed dimension, create and insert SQL statements. When used with the CmdRunner, it lets you automatically create aggregate table generation SQL.

If entered, this must be a Java class name that is an implementation of the mondrian.rolap.aggmatcher.JdbcSchema.Factory interface. The default implementation is mondrian.rolap.aggmatcher.JdbcSchema.StdFactory. Refer to the Mondrian Javadoc for more information.

Cache and SQL Generation Settings

Determines whether Jaspersoft OLAP caches the results of frequently evaluated expressions. Enabling this property can reduce the number of unnecessary computations when processing a large amount of data.

Determines whether Jaspersoft OLAP caches RolapCubeMember objects, which each associate a member of a shared hierarchy with a cube that uses it.

Disable this property if you plan to use the member cache control.

Defines the SegmentCache implementation to use. Specify the value as a fully qualified class name, such as org.example.SegmentCacheImpl (where SegmentCacheImpl is an implementation of mondrian.spi.SegmentCache).

The maximum number of threads per Jaspersoft OLAP instance that can be used to perform operations on external caches. For more information about running multiple instances in a single deployment, refer to Performance Tuning.

The maximum number of threads per Jaspersoft OLAP instance that can be used to run SQL queries when populating segments. For more information about running multiple instances in a single deployment, refer to Performance Tuning.

Determines whether data from segments are cached locally. To create custom caches, implement the SegmentCache SPI (Schema Processing Interface).

The maximum number of constraints in a single SQL IN clause. This value varies with your RDBMS type and configuration. Jaspersoft recommends these values:

When enabled, Jaspersoft OLAP pushes down to the database processing related to some NON-EMPTY CrossJoin MDX statements.

When enabled, Jaspersoft OLAP pushes down to the database processing related to some TopCount MDX statements.

When enabled, Jaspersoft OLAP pushes down to the database processing related to some Filter() MDX statements.

When enabled, Jaspersoft OLAP pushes down to the database processing related to some NON-EMPTY MDX set operations (such as member.children, level.members, and member.descendants).

When enabled, Jaspersoft OLAP expands non-native sub-expressions of a native expression into MemberLists.

When enabled, some queries against members of high levels of snowflake dimensions are more expensive. When disabled, and some rows in an outer snowflake table are not referenced by a row in an inner snowflake table, some queries return members that have no children.

Specifies the error level (OFF, WARN, or ERROR) to use when a function’s native evaluation is enabled but is not supported in the context of a particular query's usage. Errors are only returned in the case of a NonEmptyCrossJoin.

Alerts are only raised when there is a possibility that native evaluation would improve matters.

When enabled, Jaspersoft OLAP combines some rollup queries using group by grouping sets. Note that this property only applies to data stored in Oracle, DB2, or Teradata.

XML/A Settings

Limits the number of rows returned from an XML/A drill-through operation.

If this property is enabled, the first row returned for an XML/A drill-through request shows the total count of rows in the underlying database.

Determines the frequency of refreshes to the list of XML/A catalogs in a remote server. Values can be suffixed with units of measures for time, such as:

If no unit of measure is specified, Jaspersoft OLAP assumes that the unit is milliseconds.

Memory Monitoring Settings

When enabled, Jaspersoft OLAP uses the Java’s memory monitoring capability. In this case, when memory is exhausted, Jaspersoft OLAP returns a MemoryLimitExceededException exception rather than an out of memory error.

Specifies the percent of memory usage that should trigger a notification to Jaspersoft OLAP that memory is low.

Defines the number of previous execution instances the Jaspersoft OLAP keeps in its history so that it can send the events that happen thereafter. Setting this property too high can cause the Java Virtual Machine to run out of memory. Setting it too low can prevent some events from reaching the monitor's listeners.