configuration.html

基于mondrian 开源框架进行OLAP多维分析

      <td>false</td>
      <td>Whether to read aggregate tables.<p>
      If set to true, then Mondrian scans the database for aggregate tables. Unless <code>
      mondrian.rolap. aggregates.Use</code> is set to true, the aggregates found will
      not be used.</p></td>
    </tr>
    <tr>

      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#ChooseAggregateByVolume">
      mondrian.rolap.aggregates.ChooseByVolume</a></code></td>
      <td>boolean</td>
      <td>false</td>
      <td>Whether to choose an aggregate tables based volume or row
      count.<p>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.</td>

    </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#AggregateRules">
      mondrian.rolap.aggregates.rules</a></code></td>
      <td>string</td>
      <td>&quot;/DefaultRules.xml&quot;<br>

      (which is in the <code>mondrian.rolap.aggmatcher</code>
      package in <code>mondrian.jar</code>)</td>
      <td>Name of the file which defines the rules for recognizing an aggregate
      table.<p>Can be either a resource in the Mondrian jar or a URL. See
      <a href="aggregate_tables.html#How_Mondrian_recognizes_Aggregate_Tables">
      aggregate table rules</a> for details.</p>

      <p>Normally, this property is not set by a user.</td>
    </tr>
    <tr>
      <td><code><a href="api/mondrian/olap/MondrianProperties.html#AggregateRuleTag">
      mondrian.rolap.aggregates.rule.tag</a></code></td>
      <td>string</td>
      <td>default</td>

      <td>The AggRule element's tag value.<br>
      <br>
      Normally, this property is not set by a user.</td>
    </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#GenerateAggregateSql">mondrian.rolap.aggregates.generateSql</a></code></td>

      <td>boolean</td>
      <td>false</td>
      <td>Whether to print the SQL code
      generated for aggregate tables.<br>
      <br>
      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.</td>
    </tr>
    
    <tr>
      <td>
        <code>
        <a href="api/mondrian/olap/MondrianProperties.html#JdbcFactoryClass">mondrian.rolap.aggregates.jdbcFactoryClass</a></code></td>
      <td>string</td>
      <td>null</td>
      <td>
      	 If specified, overrides the default StdFactory factory class which 
      	 specifies the JdbcSchema class to use for determining the tables 
      	 and columns of a data source.  The JdbcSchema class is used as part 
      	 aggregate table matcher algorithm.
      </td>
    </tr>
    
    <tr>

      <td colspan="4">

      <b><br>
      Caching</b>
      </td>
    </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#DisableCaching">mondrian.rolap.star.disableCaching</a></code></td>

      <td>boolean</td>
      <td>false</td>
      <td>Whether to clear a RolapStar's data
      cache after each query.<p>If true, RolapStar does not cache
      aggregate data from one query to the next: the cache is cleared after each
      query.</td>
    </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#EnableExpCache">mondrian.expCache.enable</a></code></td>

      <td>boolean</td>
      <td>true</td>
      <td>Controls whether to use a cache for the results of frequently
      evaluated expressions.

      <p>With the cache disabled, an expression like:<br>
      <br>
      <code>Rank([Product]. CurrentMember,<br>
      &nbsp;&nbsp;&nbsp;&nbsp;

      Order([Product].MEMBERS, [Measures].[Unit Sales]))<br>
      </code><br>
      would perform many redundant sorts.</p></td>
    </tr>
    <tr>
      <td><code><a href="api/mondrian/olap/MondrianProperties.html#FlushAfterQuery">
      mondrian.rolap.RolapResult.flushAfterEachQuery</a></code></td>

      <td>boolean</td>
      <td>false</td>
      <td>Obsolete.</td>
    </tr>
    <tr>
      <td><code><a href="api/mondrian/olap/MondrianProperties.html#EnableRolapCubeMemberCache">
      mondrian.rolap.EnableRolapCubeMemberCache</a></code></td>

      <td>boolean</td>
      <td>true</td>
      <td>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.<p>The default is <code>true</code>, that is, use 
		a cache. If you wish to use the member cache control aspects of 
		<a href="api/mondrian/olap/CacheControl.html">mondrian.olap.CacheControl</a>
		you must set this property to <code>false</code>.</td>
    </tr>
    <tr>
      <td style="vertical-align: top;" colspan="4">

      <b><br>

      SQL generation</b>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><code>
      <a href="api/mondrian/olap/MondrianProperties.html#EnableNativeCrossJoin">mondrian.native.crossjoin.enable</a></code></td>
      <td style="vertical-align: top;">boolean</td>

      <td style="vertical-align: top;">true<br>
      </td>
      <td>If enabled, some NON EMPTY <code>CrossJoin</code>
      MDX statements will be computed in the database and not within Mondrian/Java </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><code>

      <a href="api/mondrian/olap/MondrianProperties.html#EnableNativeTopCount">mondrian.native.topcount.enable</a></code></td>
      <td style="vertical-align: top;">boolean</td>
      <td style="vertical-align: top;">true<br>
      </td>
      <td>If enabled, some <code>TopCount</code>
      MDX statements will be computed in the database and not within Mondrian/Java </td>

    </tr>
    <tr>
      <td style="vertical-align: top;"><code>
      <a href="api/mondrian/olap/MondrianProperties.html#EnableNativeFilter">mondrian.native.filter.enable</a></code></td>
      <td style="vertical-align: top;">boolean</td>
      <td style="vertical-align: top;">true<br>
      </td>

      <td>If enabled, some <code>Filter()</code>
      MDX statements will be computed in the database and not within Mondrian/Java </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><code>
      <a href="api/mondrian/olap/MondrianProperties.html#EnableNativeNonEmpty">
      mondrian.native.nonempty.enable</a></code></td>

      <td style="vertical-align: top;">boolean</td>
      <td style="vertical-align: top;">true<br>
      </td>
      <td>If enabled, some NON EMPTY MDX set operations like <code>
      member.children</code>, <code>level.members</code>
      and <code>member.descendants</code> will be computed in the database and
      not within Mondrian/Java </td>

    </tr>
    <tr>
      <td style="vertical-align: top;"><code>
      <a href="api/mondrian/olap/MondrianProperties.html#ExpandNonNative">
      mondrian.native.ExpandNonNative</a></code></td>
      <td style="vertical-align: top;">boolean</td>
      <td style="vertical-align: top;">false<br>
      </td>
      <td>If set to true, expand non native sub-expressions of a native
          expression into MemberLists</td>
    </tr>
    <tr>
      <td><code><a
href="api/mondrian/olap/MondrianProperties.html#AlertNativeEvaluationUnsupported">mondrian.native.unsupported.alert</a></code></td>
      <td>string</td>
      <td>OFF</td>
      <td>Alerting action {OFF, WARN, ERROR} 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.)  Currently, alerts are
          only raised for the NonEmptyCrossJoin function.</td>
    </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#GenerateFormattedSql">
      mondrian.rolap.generate.formatted.sql</a></code></td>
      <td>boolean</td>
      <td>false</td>

      <td>Whether to pretty-print SQL generated statements.<p>If true, Mondrian
      generates SQL strings are generated in the log or output in pretty-print
      mode, formatted for ease of reading.</td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><code>
      <a href="api/mondrian/olap/MondrianProperties.html#MaxConstraints">
      mondrian.rolap.maxConstraints</a></code></td>
      <td style="vertical-align: top;">int</td>

      <td style="vertical-align: top;">500</td>
      <td style="vertical-align: top;">Max number of constraints in a single
      `IN' SQL clause.<p>This value may be variant among database products and
      their runtime settings. Oracle, for example, gives the error &quot;ORA-01795:
      maximum number of expressions in a list is 1000&quot;.</p>

      <p>Recommended values:</p>
      <ul>
        <li>Oracle: 1,000</li>

        <li>DB2: 2,500</li>
        <li>Other: 10,000</li>
      </ul>
      </td>
  </tr>
    <tr>
      <td style="vertical-align: top;"><code>
      <a href="api/mondrian/olap/MondrianProperties.html#useGroupingSets">
      mondrian.rolap.groupingsets.enable</a></code></td>
      <td style="vertical-align: top;">boolean</td>

      <td style="vertical-align: top;">false</td>
      <td style="vertical-align: top;">If enabled, some rollup queries will
          be combined using <code>group by grouping sets</code>. Even if this
          property is set to true, grouping sets will be used only on supported
          Databases.
          <p>Currently grouping sets will be used only against Oracle, DB2 and
          Teradata.</p>
      </td>
  </tr>
    <tr>
      <td style="vertical-align: top;" colspan="4">

      <b><br>
      XML/A</b>
      </td>
  </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#EnableTotalCount">
      mondrian.xmla.drillthroughTotalCount.enable</a></code></td>

      <td>boolean</td>
      <td>true</td>
      <td>If enabled, first row in the result of an XML/A drill-through request
      will be filled with the total count of rows in underlying database.</td>
    </tr>
    <tr>
      <td><code><a href="api/mondrian/olap/MondrianProperties.html#MaxRows">
      mondrian.xmla.drillthroughMaxRows</a></code></td>

      <td>int</td>
      <td>1,000</td>
      <td>Limit on the number of rows returned by XML/A drill through request.</td>
    </tr>
    <tr>
      <td style="vertical-align: top;" colspan="4">

      <b><br>
      Memory monitoring</b>
      </td>
  </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#MemoryMonitor">
      mondrian.util.memoryMonitor.enable
      </a></code></td>

      <td>boolean</td>
      <td>true</td>
      <td>If enabled and one is using Java5 or above, then Mondrian
      will use the Java5 memory monitoring capability - a
      MemoryLimitExceededException exception ought be throw rather than
      a OutOfMemoryError when memory get low and the JVM will not
      crash.
      </td>
    </tr>
    <tr>
      <td><code><a href="api/mondrian/olap/MondrianProperties.html#MemoryMonitorThreshold">
      mondrian.util.memoryMonitor.percentage.threshold
      </a></code></td>

      <td>int</td>
      <td>90</td>
      <td>At what level of memory usage should Mondrian be notified that
      memory is running low.</td>
    </tr>
    <tr>
      <td style="vertical-align: top;" colspan="4">

      <b><br>Factories</b>
      </td>
  </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#MemoryMonitorClass">
      mondrian.util.MemoryMonitor.class
      </a></code></td>

      <td>string</td>
      <td>-</td>
      <td>
      By default this property does not have a value.
      If set, then it is the class name of an implementation of
      the MemoryMonitor class and is used by the
      MemoryMonitorFactory to create the single instance.
      </td>
    </tr>
    <tr>
      <td><code>
      <a href="api/mondrian/olap/MondrianProperties.html#ExpCompilerClass">
      mondrian.calc.ExpCompiler.class
      </a></code></td>

      <td>string</td>
      <td>-</td>
      <td>
      By default this property does not have a value.
      If set, then it is the class name of an implementation of
      the ExpCompiler class and is used by the
      ExpCompiler.Factory to create each instance.
      </td>
    </tr>

</table>

<h3>Limit properties<a name="Limit_properties">&nbsp;</a></h3>

<p>Properties <code>mondrian.result.limit</code>, <code>mondrian.rolap.iterationLimit</code>
and <code>mondrian.rolap.queryTimeout</code> enforce runtime limits on the
time or space required to execute a query. If any of these limits are exceeded,
mondrian throws an exception which extends
<a href="api/mondrian/olap/ResultLimitExceededException.html">
mondrian.olap.ResultLimitExceededException</a>.</p>

<h2>Connect strings<a name="Connect_strings">&nbsp;</a></h2>

<h3>Connect string syntax<a name="Connect_string_syntax">&nbsp;</a></h3>

<p>Mondrian connect strings are a connection of property/value pairs, of the
form 'property=value;property=value;...'.</p>

<p>Values can be enclosed in single-quotes, which allows them to contain spaces
and punctuation. See the the
<a target="_blank" href="http://msdn.microsoft.com/library/en-us/oledb/htm/oledbconnectionstringsyntax.asp">
OLE DB connect string syntax specification</a>.</p>