123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178 |
- # Licensed Materials - Property of IBM
- # IBM Cognos Products: OQP
- # (C) Copyright IBM Corp. 2005, 2015
- # US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM corp.
- # === Capabilities for Cognos ROLAP ===
- #
- # OLAP Metadata
- #
- # Nothing here so far ...
- #
- # OLAP Data
- #
- # Indicates if this provider supports the currency units.
- olap.data.supportCurrencyUnits=false
- # Indicates if this provider supports the setting of MDXMissingMemberMode for data queries.
- olap.data.supportMDXMissingMemberMode=false
- #
- # MDX Optimizations
- # This configuration flags says whether the provider supports replacing the aggregate of child members with the parent
- # when XQE believes this will be true. This is not guaranteed to work for all providers, so this setting must default
- # to false.
- #
- mdx.optimize.parentmember=true
- #
- # MDX Function Support
- #
- mdx.support.setalias=true
- #
- # MDX flag for turning on/off the removeNonExistentTuples feature. This is an overriding
- # setting over all the ROLAP cubes. The same setting can be changed per cube and here is the
- # expected behaviour where T:true, F:false, N: not defined:
- #
- # ro.properties cube model result
- # T T T
- # T F F
- # T N(T) T
- # F T F
- # F F F
- # F N(T) F
- # N(F) T F
- # N(F) F F
- # N(F) N(T) F
- #
- # Basicaly, when mdx.set.removeNonExistentTuples=true, we look at the cube setting.
- # When mdx.set.removeNonExistentTuples=false, this feature is turned off regardless
- # of the cube setting.
- mdx.set.removeNonExistentTuples=true
- #
- # MDX Support for OLYMPIC rank with implicit sort
- #
- mdx.support.olympicRankSort=false
- #
- # Use Local OLAP (LOLAP) for functions
- #
- v5.useLOLAPForFunctions=true
- #
- # Null behavior of order function (TopCount, BottomCount) in the MDX engine.
- # Nulls treated like zero by default.
- #
- null.order.function=zero
- #
- # Null value position with sort function. This flag is associated with null.order.function.
- # null.order.function null.position.order.function behavior
- # null first null + first in the list
- # null last null + last in the list
- # null stable_else_first null + first in the list (stable here has no effect)
- # null stable_else_last null + last in the list (stable here has no effect)
- # zero first for numeric NULL: it's the less than zero larger than smallest negative number. This is the standard MDX behavior.
- # For non-numeric null: null + first in the list
- # zero last for numeric NULL: it's the greater than zero smaller than smallest positve number.
- # For non-numeric null: null + last in the list
- # zero stable_else_first nulls are equal to zero and will turn in stable order when sorted against zero. For non-numeric null: null + first in the list
- # zero stable_else_last nulls are equal to zero and will turn in stable order when sorted against zero. For non-numeric null: null + last in the list
- null.position.order.function=STABLE_ELSE_FIRST
- #
- # If true, ROLAP will push down the evaluation of the TopBottomCount expression to the relational database
- #
- pushdownTopBottomCountToRelational=true
- #
- # If true, ROLAP will push down the evaluation of the TopPercent/Sum expression to the relational database
- #
- pushdownTopPercentSumToRelational=true
- #
- # If true, ROLAP will push down the evaluation of the Filter expression to the relational database
- #
- pushdownFilterToRelational=true
- #
- # If true, ROLAP will push down the evaluation of calculations in filter pushdown to the relational database
- #
- pushdownCalculationsInFilterPushdownToRelational=false
- #
- # If true, the input set for the Topcount operator is filtered when pushdown is on
- #
- enableFilterSetInPushDownMode=false
- #
- # If true, the coalesce function is used for rank when pushdown is on.
- #
- enableCoalesceRankInPushDownMode=false
- #
- # If true, the coalesce function is used for filter when pushdown is on.
- #
- enableCoalesceFilterInPushDownMode=false
- #
- # If true, measures with firstPeriod/lastPeriod aggregates will be loaded into the cube.
- #
- enableFirstLastAggregateRulesMeasures=true
- #
- # Threshold 1: mdx.cjs.tupleToIndBitMap.threshold
- # Threshold for the use of the temporary bit map tuples-to-indexes structure for
- # cross joined sets (cjs).
- # This structure is used to save memory but it could slow down the execution.
- # Threshold2: mdx.cjs.noTupleIndex.threshold
- # Threshold for skipping the use of a tuples-to-indexes structure because the set is too
- # big to index in memory
- # Threshold 3: mdx.cjs.maxTupleMaterialization.threshold
- # Multiplication factor used to determine whether a tuples-to-indexes structure
- # that is optimized for many nested crossjoined sets (where iterating over the resulting
- # tuples is expensive) should be used
- #
- # mdx.cjs.tupleToIndBitMap.threshold=25000
- # mdx.cjs.maxTupleMaterialization.threshold=1000
- mdx.cjs.noTupleIndex.threshold=1000000000000
- #
- # Threshold controlling if result set cell storage should be in memory or in stream.
- # Set it to 0 to disable using in stream cell storage
- #
- mdx.cjs.maxCellsInMemory.threshold=1000000000000
- #
- # Specify whether or not the provider will be sub-queried for MUNs.
- # This feature is not required for this datasource and thefore not supported.for it
- #
- queryProviderForMUNs=false
- #
- # This property controls how to handle the projection of nested levels of the same hierarchy.
- # Specifically the use of the technique involving nested level decoration rules.
- # In that case the planner queries only the lowest level members, later the post-processing queries the outer levels if required.
- # - always: always use this technique
- # - never: never use this technique
- # - automatic: allow the planner to decide whether to use or not this technique.
- #
- applyNestedLevelDecorationRules=always
- #
- # Does the provider support caching of named sets between queries in the local MDX engine.
- #
- mdx.support.namedSetCaching=true
- #
- # When set to TRUE the named sets will be treated as context dependent.
- #
- mdx.support.namedSetDynamic=true
|