mondrian.rolap.aggregates.rule.tag
String property that is the AggRule element's tag value.
Normally, this property is not set by a user.
mondrian.rolap.aggregates.rules
String property containing the name of the file which defines the rules for recognizing an aggregate table. Can be either a resource in the Mondrian jar or a URL.
The default value is "/DefaultRules.xml", which is in the mondrian.rolap.aggmatcher package in Mondrian.jar.
Normally, this property is not set by a user.
mondrian.rolap.aggregates.ChooseByVolume
Boolean property that controls whether aggregate tables are ordered by their volume or row count.
If true, Mondrian uses the aggregate table with the smallest volume (number of rows multiplied by number of columns); if false, Mondrian uses the aggregate table with the fewest rows.
mondrian.rolap.aggregates.generateSql
Boolean property that controls whether to print the SQL code generated for aggregate tables.
If set, then as each aggregate request is processed, both the lost and collapsed dimension create and insert sql code is printed. This is for use in the CmdRunner allowing one to create aggregate table generation sql.
mondrian.rolap.aggregates.jdbcFactoryClass
Property that defines the JdbcSchema factory class which determines the list of tables and columns of a specific datasource.
@see mondrian.rolap.aggmatcher.JdbcSchemamondrian.rolap.aggregates.optimizePredicates
Boolean property that determines whether Mondrian optimizes predicates.
If true, Mondrian may retrieve a little more data than specified in MDX query and cache it for future use. For example, if you ask for data on 48 states of the United States for 3 quarters of 2011, Mondrian will round out to all 50 states and all 4 quarters. If false, Mondrian still optimizes queries that involve all members of a dimension.
mondrian.rolap.aggregates.Read
Boolean property that determines whether Mondrian should read aggregate tables.
If set to true, then Mondrian scans the database for aggregate tables. Unless mondrian.rolap.aggregates.Use is set to true, the aggregates found will not be used.
mondrian.rolap.aggregates.Use
Boolean property that controls whether Mondrian uses aggregate tables.
If true, then Mondrian uses aggregate tables. This property is queried prior to each aggregate query so that changing the value of this property dynamically (not just at startup) is meaningful.
Aggregates can be read from the database using the {@link #ReadAggregates} property but will not be used unless this property is set to true.
mondrian.rolap.star.disableCaching
mondrian.rolap.star.disableLocalSegmentCache
mondrian.expCache.enable
Rank([Product].CurrentMember,
Order([Product].MEMBERS, [Measures].[Unit Sales]))
would perform
many redundant sorts. The default is true.
mondrian.rolap.EnableRolapCubeMemberCache
Property that determines whether to cache RolapCubeMember objects, each of which associates a member of a shared hierarchy with a particular cube in which it is being used.
The default is {@code true}, that is, use a cache. If you wish to use the member cache control aspects of {@link mondrian.olap.CacheControl}, you must set this property to {@code false}.
RolapCubeMember has recently become more lightweight to construct, and we may obsolete this cache and this property.
mondrian.spi.dataSourceResolverClass
Property that defines the name of the plugin class that resolves data source names to {@link javax.sql.DataSource} objects. The class must implement the {@link mondrian.spi.DataSourceResolver} interface. If not specified, the default implementation uses JNDI to perform resolution.
Example:
mondrian.spi.dataSourceResolverClass=mondrian.spi.impl.JndiDataSourceResolver
mondrian.calc.ExpCompiler.class
Property that defines the name of the class used to compile scalar expressions.
If the value is
non-null, it is used by the ExpCompiler.Factory
to create the implementation.
To test that for all test MDX queries that all functions can handle requests for ITERABLE, LIST and MUTABLE_LIST evaluation results, use the following:
mondrian.calc.ExpCompiler.class=mondrian.olap.fun.ResultStyleCompiler
mondrian.util.MemoryMonitor.class
Property that defines the name of the class used as a memory monitor.
If the value is
non-null, it is used by the MemoryMonitorFactory
to create the implementation.
mondrian.rolap.RolapMember.PropertyValueMapFactory.class
Property that defines the name of the factory class used to create maps of member properties to their respective values.
If the value is
non-null, it is used by the PropertyValueFactory
to create the implementation. If unset,
{@link mondrian.rolap.RolapMemberBase.DefaultPropertyValueMapFactory}
will be used.
mondrian.rolap.SqlMemberSource.ValuePoolFactory.class
Property that defines the name of the class used in SqlMemberSource to pool common values.
If the value is non-null, it is used by the
SqlMemberSource.ValueMapFactory
to create the implementation. If it is not set, then
{@link mondrian.rolap.SqlMemberSource.NullValuePoolFactory}
will be used, meaning common values will not be pooled.
mondrian.rolap.cancelPhaseInterval
Positive integer property that determines how many rows are read from sql executions between checks for whether the current mdx query has been cancelled.
Setting the interval too small may result in a performance hit when reading large result sets;
setting it too high can cause a big delay between the query being marked as cancelled and system resources associated to it being released.
mondrian.olap.case.sensitive
mondrian.rolap.cellBatchSize
mondrian.rolap.compareSiblingsByOrderKey
mondrian.olap.fun.crossjoin.optimizer.size
Property that defines when to apply the crossjoin optimization algorithm.
If a crossjoin input list's size is larger than this property's
value and the axis has the "NON EMPTY" qualifier, then
the crossjoin non-empty optimizer is applied.
Setting this value to '0' means that for all crossjoin
input lists in non-empty axes will have the optimizer applied.
On the other hand, if the value is set larger than any possible
list, say Integer.MAX_VALUE
, then the optimizer
will never be applied.
mondrian.rolap.agg.enableCacheHitCounters
Property that controls whether aggregation cache hit / miss counters will be enabled.
Note that this will affect performance due to existence of sync blocks.
@deprecated This property is no longer used, and will be removed in mondrian-4.0.mondrian.drillthrough.enable
mondrian.rolap.EnableInMemoryRollup
true
.
mondrian.rolap.nonempty
mondrian.olap.triggers.enable
Boolean property that controls whether to notify the Mondrian system when a {@link MondrianProperties property value} changes.
This allows objects dependent on Mondrian properties to react (that
is, reload), when a given property changes via, say,
MondrianProperties.instance().populate(null)
or
MondrianProperties.instance().QueryLimit.set(50)
.
mondrian.result.highCardChunkSize
mondrian.rolap.ignoreInvalidMembers
Property that defines whether non-existent member errors should be ignored during schema load. If so, the non-existent member is treated as a null member.
mondrian.rolap.ignoreInvalidMembersDuringQuery
Property that defines whether non-existent member errors should be ignored during query validation. If so, the non-existent member is treated as a null member.
mondrian.olap.agg.IgnoreMeasureForNonJoiningDimension
Property that defines whether to ignore measure when non joining dimension is in the tuple during aggregation.
If there are unrelated dimensions to a measure in context during aggregation, the measure is ignored in the evaluation context. This behaviour kicks in only if the CubeUsage for this measure has IgnoreUnrelatedDimensions attribute set to false.
For example, Gender doesn't join with [Warehouse Sales] measure.
With mondrian.olap.agg.IgnoreMeasureForNonJoiningDimension=true Warehouse Sales gets eliminated and is ignored in the aggregate value.
[Store Sales] + [Warehouse Sales]
SUM({Product.members * Gender.members}) 7,913,333.82
With mondrian.olap.agg.IgnoreMeasureForNonJoiningDimension=false Warehouse Sales with Gender All level member contributes to the aggregate value.
[Store Sales] + [Warehouse Sales]
SUM({Product.members * Gender.members}) 9,290,730.03
On a report where Gender M, F and All members exist a user will see a large aggregated value compared to the aggregated value that can be arrived at by summing up values against Gender M and F. This can be confusing to the user. This feature can be used to eliminate such a situation.
mondrian.rolap.iterationLimit
Integer property indicating the maximum number of iterations allowed when iterating over members to compute aggregates. A value of 0 (the default) indicates no limit.
mondrian.jdbcDrivers
mondrian.rolap.precache.threshold
Property which governs whether child members or members of a level are precached
when child or level members are requested within a
query expression. For example,
if an expression references two child members in the store dimension,
like { [Store].[USA].[CA], [Store].[USA].[OR] }
, precaching will
load *all* children under [USA] rather than just the 2 requested.
The threshold value is
compared against the cardinality of the level to determine
whether or not precaching should be performed. If cardinality is
lower than the threshold value Mondrian will precache. Setting
this property to 0 effectively disables precaching.
mondrian.rolap.localePropFile
String property that holds the name of the class whose resource bundle is to be used to for this schema. For example, if the class is {@code com.acme.MyResource}, mondrian will look for a resource bundle called {@code com/acme/MyResource_locale.properties} on the class path. (This property has a confusing name because in a previous release it actually held a file name.)
Used for the {@link mondrian.i18n.LocalizingDynamicSchemaProcessor}; see Internationalization for more details.
Default value is null.
log4j.configuration
Set mondrian logging information if not provided by containing application.
Examples:
log4j.configuration=file://full/path/log4j.xml
log4j.configuration=file:log4j.properties
mondrian.rolap.evaluate.MaxEvalDepth
Boolean property that defines the maximum number of passes allowable while evaluating an MDX expression.
If evaluation exceeds this depth (for example, while evaluating a very complex calculated member), Mondrian will throw an error.
mondrian.native.NativizeMaxResults
Property that controls the maximum number of results contained in a NativizeSet result set.
If the number of tuples contained in the result set exceeds this value Mondrian throws a LimitExceededDuringCrossjoin error.
mondrian.native.NativizeMinThreshold
Property that controls minimum expected cardinality required in order for NativizeSet to natively evaluate a query.
If the expected cardinality falls below this level the query is executed non-natively.
It is possible for the actual cardinality to fall below this threshold even though the expected cardinality falls above this threshold. In this case the query will be natively evaluated.
mondrian.olap.elements.NeedDimensionPrefix
Property determines if elements of dimension (levels, hierarchies, members) need to be prefixed with dimension name in MDX query.
For example when the property is true, the following queries will error out. The same queries will work when this property is set to false.
select {[M]} on 0 from sales
select {[USA]} on 0 from sales
select {[USA].[CA].[Santa Monica]} on 0 from sales
When the property is set to true, any query where elements are prefixed with dimension name as below will work
select {[Gender].[F]} on 0 from sales
select {[Customers].[Santa Monica]} on 0 from sales
Please note that this property does not govern the behaviour wherein
[Gender].[M]
is resolved into a fully qualified
[Gender].[M]
In a scenario where the schema is very large and dimensions have large number of members a MDX query that has a invalid member in it will cause mondrian to to go through all the dimensions, levels, hierarchies, members and properties trying to resolve the element name. This behavior consumes considerable time and resources on the server. Setting this property to true will make it fail fast in a scenario where it is desirable.
mondrian.olap.NullDenominatorProducesNull
Property that defines the behavior of division if the denominator evaluates to zero.
If false (the default), if a division has a non-null numerator and a null denominator, it evaluates to "Infinity", which conforms to SSAS behavior.
If true, the result is null if the denominator is null. Setting to true enables the old semantics of evaluating this to null; this does not conform to SSAS, but is useful in some applications.
mondrian.olap.NullMemberRepresentation
Property that determines how a null member value is represented in the result output.
AS 2000 shows this as empty value
AS 2005 shows this as "(null)" value
mondrian.query.limit
Maximum number of simultaneous queries the system will allow.
Oracle fails if you try to run more than the 'processes' parameter in init.ora, typically 150. The throughput of Oracle and other databases will probably reduce long before you get to their limit.
mondrian.rolap.queryTimeout
Property that defines the timeout value (in seconds) for queries. A value of 0 (the default) indicates no timeout.
mondrian.result.limit
mondrian.rolap.maxQueryThreads
Maximum number of MDX query threads per Mondrian server instance. Defaults to 20.
mondrian.rolap.shepherdThreadPollingInterval
Property that defines the interval value between polling operations performed by the RolapConnection shepherd thread. This controls query timeouts and cancellation, so a small value (a few milliseconds) is best. Setting this to a value higher than mondrian.rolap.queryTimeout will result the timeout not being enforced as expected.
Default value is "1000ms". Default time unit is "ms".
mondrian.rolap.SegmentCache
org.example.SegmentCacheImpl
where SegmentCacheImpl
is an implementation of {@link mondrian.spi.SegmentCache}.
mondrian.rolap.maxCacheThreads
Maximum number of threads per Mondrian server instance that are used to run perform operations on the external caches. Defaults to 100.
mondrian.rolap.maxSqlThreads
Maximum number of threads per Mondrian server instance that are used to run SQL queries when populating segments. Defaults to 100.
mondrian.rolap.SolveOrderMode
Valid values are "scoped" and "absolute" (the default). See {@link mondrian.olap.SolveOrderMode} for details.
mondrian.rolap.SparseSegmentValueThreshold
Property that, with {@link #SparseSegmentDensityThreshold}, determines whether to choose a sparse or dense representation when storing collections of cell values in memory.
When storing collections of cell values, Mondrian has to choose
between a sparse and a dense representation, based upon the
possible
and actual
number of values.
The density
is actual / possible
.
We use a sparse representation if
(possible -
{@link #SparseSegmentCountThreshold countThreshold}) *
{@link #SparseSegmentDensityThreshold densityThreshold} >
actual
For example, at the default values ({@link #SparseSegmentCountThreshold countThreshold} = 1000, {@link #SparseSegmentDensityThreshold} = 0.5), we use a dense representation for
Any fewer actual values, or any more possible values, and Mondrian will use a sparse representation.
mondrian.rolap.SparseSegmentDensityThreshold
mondrian.olap.SsasCompatibleNaming
Property that defines whether to enable new naming behavior.
If true, hierarchies are named [Dimension].[Hierarchy]; if false, [Dimension.Hierarchy].
mondrian.statistics.providers
Comma-separated list of classes to be used to get statistics about the number of rows in a table, or the number of distinct values in a column.
If there is a value for mondrian.statistics.providers.DATABASE, where DAtABASE is the current database name (e.g. MYSQL or ORACLE), then that property overrides.
Example:
mondrian.statistics.providers=mondrian.spi.impl.JdbcStatisticsProvider
mondrian.statistics.providers.MYSQL=mondrian.spi.impl.JdbcStatisticsProvider,mondrian.spi.impl.JdbcStatisticsProvider
This would use JDBC's statistics (via the java.sql.DatabaseMetaData.getIndexInfo method) for most databases, but for connections to a MySQL database, would use external statistics first, and fall back to JDBC statistics only if external statistics were not available.
mondrian.test.highCardDimensions
mondrian.webapp.connectString
Connect string for the webapp. (Used by the webapp only.)
To achieve access control, append say ;Role='California
manager'
to the connect string.
mondrian.webapp.deploy
Where mondrian.war will be deployed to. (Used by mondrian's build.xml ant file only.)
Example: mondrian.webapp.deploy=C:/jboss-4.0.2/server/default/deploy
mondrian.xmla.SchemaRefreshInterval
Interval at which to refresh the list of XML/A catalogs. (Usually known as the datasources.xml file.)
It is not an active process; no threads will be created. It only serves as a rate limiter. The refresh process is triggered by requests to the doPost() servlet method.
Values may have time unit suffixes such as 's' (second) or 'ms' (milliseconds). Default value is 3000 milliseconds (3 seconds). Default time unit is milliseconds.
See also {@link mondrian.xmla.impl.DynamicDatasourceXmlaServlet}.
mondrian.server.monitor.executionHistorySize
Property that defines how many previous execution instances the
Monitor
keeps in its history so that it can send the events
which happen after the fact. Setting this property too high will make the
JVM run out of memory. Setting it too low might prevent some events from
reaching the listeners of the monitor.
This property is for internal use only and should not be changed unless required. Defaults to 1,000.
mondrian.util.memoryMonitor.enable
Property that defines whether the MemoryMonitor
should
be enabled. By default it is disabled; memory monitor is not available
before Java version 1.5.
mondrian.util.memoryMonitor.percentage.threshold
Property that defines the default MemoryMonitor
percentage threshold. If enabled, when Java's memory monitor detects
that post-garbage collection is above this value, notifications are
generated.
mondrian.native.unsupported.alert
Alerting action to take in case native evaluation of a function is enabled but not supported for that function's usage in a particular query. (No alert is ever raised in cases where native evaluation would definitely have been wasted effort.)
Recognized actions:
OFF
: do nothing (default action, also used if
unrecognized action is specified)WARN
: log a warning to RolapUtil loggerERROR
: throw an instance of
{@link NativeEvaluationUnsupportedException}mondrian.rolap.groupingsets.enable
Property that defines
whether to generate SQL queries using the GROUPING SETS
construct for rollup. By default it is not enabled.
Ignored on databases which do not support the
GROUPING SETS
construct (see
{@link mondrian.spi.Dialect#supportsGroupingSets}).
mondrian.native.crossjoin.enable
mondrian.native.filter.enable
mondrian.native.nonempty.enable
If enabled some NON EMPTY set operations like member.children, level.members and member descendants will be computed in SQL.
mondrian.native.topcount.enable
mondrian.native.ExpandNonNative
mondrian.rolap.FilterChildlessSnowflakeMembers
Property that defines whether to generate joins to filter out members in a snowflake dimension that do not have any children.
If true (the default), some queries to query members of high levels snowflake dimensions will be more expensive. If false, and if there are rows in an outer snowflake table that are not referenced by a row in an inner snowflake table, then some queries will return members that have no children.
Our recommendation, for best performance, is to remove rows outer snowflake tables are not referenced by any row in an inner snowflake table, during your ETL process, and to set this property to {@code false}.
mondrian.rolap.generate.formatted.sql
Boolean property that controls pretty-print mode.
If true, the all SqlQuery SQL strings will be generated in pretty-print mode, formatted for ease of reading.
mondrian.rolap.maxConstraints
Max number of constraints in a single 'IN' SQL clause.
This value may be variant among database products and their runtime settings. Oracle, for example, gives the error "ORA-01795: maximum number of expressions in a list is 1000".
Recommended values:
mondrian.catalogURL
mondrian.foodmart.jdbcURL
Property containing the JDBC URL of the FoodMart database. The default value is to connect to an ODBC data source called "MondrianFoodMart".
To run the test suite, first load the FoodMart data set into the database of your choice. Then set the driver.classpath, mondrian.foodmart.jdbcURL and mondrian.jdbcDrivers properties, by un-commenting and modifying one of the sections below. Put the JDBC driver jar into mondrian/testlib.
Here are example property settings for various databases.
mondrian.foodmart.jdbcURL=jdbc:derby:demo/derby/foodmart
mondrian.foodmart.jdbcUser=sa
mondrian.foodmart.jdbcPassword=sa
mondrian.jdbcDrivers=org.apache.derby.jdbc.EmbeddedDriver
driver.classpath=testlib/derby.jar
mondrian.foodmart.jdbcURL=jdbc:firebirdsql:localhost/3050:/mondrian/foodmart.gdb
mondrian.jdbcDrivers=org.firebirdsql.jdbc.FBDriver
driver.classpath=/jdbc/fb/firebirdsql-full.jar
mondrian.foodmart.jdbcURL=jdbc:postgresql://localhost/foodmart?user=gpadmin&password=xxxx
mondrian.foodmart.jdbcUser=foodmart
mondrian.foodmart.jdbcPassword=foodmart
mondrian.jdbcDrivers=org.postgresql.Driver
driver.classpath=lib/postgresql-8.2-504.jdbc3.jar
mondrian.foodmart.jdbcURL=jdbc:luciddb:http://localhost
mondrian.foodmart.jdbcUser=foodmart
mondrian.jdbcDrivers=org.luciddb.jdbc.LucidDbClientDriver
driver.classpath=/path/to/luciddb/plugin/LucidDbClient.jar
oracle.home=G:/oracle/product/10.1.0/Db_1
mondrian.foodmart.jdbcURL.oracle=jdbc:oracle:thin:@//host:port/service_name
mondrian.foodmart.jdbcURL=jdbc:oracle:thin:foodmart/foodmart@//stilton:1521/orcl
mondrian.foodmart.jdbcURL=jdbc:oracle:oci8:foodmart/foodmart@orcl
mondrian.foodmart.jdbcUser=FOODMART
mondrian.foodmart.jdbcPassword=oracle
mondrian.jdbcDrivers=oracle.jdbc.OracleDriver
driver.classpath=/home/jhyde/open/mondrian/lib/ojdbc14.jar
mondrian.foodmart.jdbcURL=jdbc:odbc:MondrianFoodMart
mondrian.jdbcDrivers=sun.jdbc.odbc.JdbcOdbcDriver
driver.classpath=
mondrian.foodmart.jdbcURL=jdbc:hsqldb:demo/hsql/FoodMart
mondrian.jdbcDrivers=org.hsqldb.jdbcDriver
driver.classpath=xx
mondrian.foodmart.jdbcURL=jdbc:mysql://localhost/foodmart?user=foodmart&password=foodmart
mondrian.foodmart.jdbcURL=jdbc:mysql://localhost/foodmart
mondrian.foodmart.jdbcUser=foodmart
mondrian.foodmart.jdbcPassword=foodmart
mondrian.jdbcDrivers=com.mysql.jdbc.Driver
driver.classpath=D:/mysql-connector-3.1.12
mondrian.foodmart.jdbcURL=jdbc:com.nuodb://localhost/foodmart?schema=mondrian
mondrian.foodmart.jdbcUser=foodmart
mondrian.foodmart.jdbcPassword=foodmart
mondrian.jdbcDrivers=com.nuodb.jdbc.Driver
mondrian.foodmart.jdbcSchema=mondrian
driver.classpath=/opt/nuodb/jar/nuodbjdbc.jar
As MySQL. (Infobright uses a MySQL driver, version 5.1 and later.)
mondrian.foodmart.jdbcURL=jdbc:ingres://192.168.200.129:II7/MondrianFoodMart;LOOP=on;AUTO=multi;UID=ingres;PWD=sergni
mondrian.jdbcDrivers=com.ingres.jdbc.IngresDriver
driver.classpath=c:/ingres2006/ingres/lib/iijdbc.jar
mondrian.foodmart.jdbcURL=jdbc:postgresql://localhost/FM3
mondrian.foodmart.jdbcUser=postgres
mondrian.foodmart.jdbcPassword=pgAdmin
mondrian.jdbcDrivers=org.postgresql.Driver
mondrian.foodmart.jdbcURL=jdbc:hpt4jdbc://localhost:18650/:schema=PENTAHO;serverDataSource=PENTAHO_DataSource
mondrian.foodmart.jdbcUser=user
mondrian.foodmart.jdbcPassword=password
mondrian.jdbcDrivers=com.hp.t4jdbc.HPT4Driver
driver.classpath=/some/path/hpt4jdbc.jar
mondrian.foodmart.jdbcURL=jdbc:netezza://127.0.1.10/foodmart
mondrian.foodmart.jdbcUser=user
mondrian.foodmart.jdbcPassword=password
mondrian.jdbcDrivers=org.netezza.Driver
driver.classpath=/some/path/nzjdbc.jar
mondrian.foodmart.jdbcURL=jdbc:jtds:sybase://xxx.xxx.xxx.xxx:port/dbName
mondrian.foodmart.jdbcUser=user
mondrian.foodmart.jdbcPassword=password
mondrian.jdbcDrivers=net.sourceforge.jtds.jdbc.Driver
driver.classpath=/some/path/jtds-1.2.jar
mondrian.foodmart.jdbcURL=jdbc:teradata://DatabaseServerName/DATABASE=FoodMart
mondrian.foodmart.jdbcUser=user
mondrian.foodmart.jdbcPassword=password
mondrian.jdbcDrivers=com.ncr.teradata.TeraDriver
driver.classpath=/some/path/terajdbc/classes/terajdbc4.jar
mondrian.foodmart.jdbcURL=jdbc:vertica://xxx.xxx.xxx.xxx:port/dbName
mondrian.foodmart.jdbcUser=user
mondrian.foodmart.jdbcPassword=password
mondrian.jdbcDrivers=com.vertica.Driver
driver.classpath=/some/path/vertica.jar
mondrian.foodmart.jdbcURL=jdbc:ingres://xxx.xxx.xxx.xxxport/dbName
mondrian.foodmart.jdbcUser=user
mondrian.foodmart.jdbcPassword=password
mondrian.jdbcDrivers=com.ingres.jdbc.IngresDriver
driver.classpath=/some/path/iijdbc.jar
mondrian.test.Iterations
mondrian.test.QueryFileDirectory
mondrian.test.QueryFilePattern
querywhatever.xml
in the directory.
Example:
mondrian.test.QueryFilePattern=queryTest_fec[A-Za-z0-9_]*.xml
mondrian.test.Class
String property that determines which test class to run.
This is the name of the class. It must either implement {@code junit.framework.Test} or have a method {@code public [static] junit.framework.Test suite()}.
Example:
mondrian.test.Class=mondrian.test.FoodMartTestCase
@see #TestName
mondrian.test.connectString
Property containing the connect string which regression tests should use to connect to the database.
Format is specified in {@link Util#parseConnectString(String)}.
mondrian.test.ExpDependencies
Integer property that controls whether to test operators' dependencies, and how much time to spend doing it.
If this property is positive, Mondrian's test framework allocates an expression evaluator which evaluates each expression several times, and makes sure that the results of the expression are independent of dimensions which the expression claims to be independent of.
The default is 0.
mondrian.foodmart.jdbcPassword
mondrian.foodmart.jdbcUser
mondrian.test.Name
String property that determines which tests are run.
This is a regular expression as defined by {@link java.util.regex.Pattern}. If this property is specified, only tests whose names match the pattern in its entirety will be run.
@see #TestClassmondrian.test.random.seed
Seed for random number generator used by some of the tests.
Any value besides 0 or -1 gives deterministic behavior. The default value is 1234: most users should use this. Setting the seed to a different value can increase coverage, and therefore may uncover new bugs.
If you set the value to 0, the system will generate its own pseudo-random seed.
If you set the value to -1, Mondrian uses the next seed from an internal random-number generator. This is a little more deterministic than setting the value to 0.
mondrian.test.TimeLimit
mondrian.test.VUsers
mondrian.test.Warmup
mondrian.test.WarnIfNoPatternForDialect
Property that controls whether warning messages should be printed if a SQL comparison test does not contain expected SQL statements for the specified dialect. The tests are skipped if no expected SQL statements are found for the current dialect.
Possible values are the following:
Specific tests can overwrite the default setting. The priority is:
mondrian.xmla.drillthroughTotalCount.enable
mondrian.xmla.drillthroughMaxRows