Skip to content

KxClusterCodeDeploymentConfiguration

Used by
Source code in docs_src/capo_finspace/types/kx_cluster_code_deployment_configuration.py 
13
14
15
class KxClusterCodeDeploymentConfiguration(TypedDict, closed=True):
    deployment_strategy: "capo_finspace.types.kx_cluster_code_deployment_strategy.KxClusterCodeDeploymentStrategy"
    """<p> The type of deployment that you want on a cluster. </p> <ul> <li> <p>ROLLING – This options updates the cluster by stopping the exiting q process and starting a new q process with updated configuration.</p> </li> <li> <p>NO_RESTART – This option updates the cluster without stopping the running q process. It is only available for <code>GP</code> type cluster. This option is quicker as it reduces the turn around time to update configuration on a cluster. </p> <p>With this deployment mode, you cannot update the <code>initializationScript</code> and <code>commandLineArguments</code> parameters.</p> </li> <li> <p>FORCE – This option updates the cluster by immediately stopping all the running processes before starting up new ones with the updated configuration. </p> </li> </ul>"""

deployment_strategy instance-attribute 

deployment_strategy: KxClusterCodeDeploymentStrategy

The type of deployment that you want on a cluster.

  • ROLLING – This options updates the cluster by stopping the exiting q process and starting a new q process with updated configuration.

  • NO_RESTART – This option updates the cluster without stopping the running q process. It is only available for GP type cluster. This option is quicker as it reduces the turn around time to update configuration on a cluster.

    With this deployment mode, you cannot update the initializationScript and commandLineArguments parameters.

  • FORCE – This option updates the cluster by immediately stopping all the running processes before starting up new ones with the updated configuration.