Projection Parameters
The following configuration parameters help you manage projections.
Parameters | Description |
---|---|
AnalyzeRowCountInterval |
Specifies how often Vertica checks the number of projection rows and whether the threshold set by For more information, see Collecting Statistics. Default Value: 60 seconds |
ARCCommitPercentage |
Sets the threshold percentage of WOS to ROS rows, which determines when to aggregate projection row counts and commit the result to the catalog. Vertica performs this action when the WOS to ROS percentage exceeds this setting. Default Value: 3 (percent)
|
ContainersPerProjectionLimit |
Specifies how many ROS containers Vertica creates per projection before ROS pushback occurs. Default Value: 1024 Caution: Increasing this parameter's value can cause serious degradation of database performance. Vertica strongly recommends that you not modify this parameter without first consulting with Customer Support professionals. |
EnableGroupByProjections |
When set to Default Value: 1 |
EnableExprsInProjections |
When set to Default Value: 1 |
EnableTopKProjections |
When set to Default Value: 1 |
MaxAutoSegColumns |
Specifies the number of columns (0 –1024) to segment automatically when creating auto-projections from Set to Default Value: 32 |
RebalanceQueryStorageContainers |
By default, prior to performing a rebalance, Vertica performs a system table query to compute the size of all projections involved in the rebalance task. This query enables Vertica to optimize the rebalance to most efficiently utilize available disk space. This query can, however, significantly increase the time required to perform the rebalance. By disabling the system table query, you can reduce the time required to perform the rebalance. If your nodes are low on disk space, disabling the query increases the chance that a node runs out of disk space. In that situation, the rebalance fails. Default Value: 1 |
SegmentAutoProjection |
Determines whether auto-projections are segmented by default. Set to |