public static interface KxDeploymentConfiguration.Builder extends SdkPojo, CopyableBuilder<KxDeploymentConfiguration.Builder,KxDeploymentConfiguration>
| Modifier and Type | Method and Description |
|---|---|
KxDeploymentConfiguration.Builder |
deploymentStrategy(KxDeploymentStrategy deploymentStrategy)
The type of deployment that you want on a cluster.
|
KxDeploymentConfiguration.Builder |
deploymentStrategy(String deploymentStrategy)
The type of deployment that you want on a cluster.
|
equalsBySdkFields, sdkFieldscopyapplyMutation, buildKxDeploymentConfiguration.Builder deploymentStrategy(String deploymentStrategy)
The type of deployment that you want on a cluster.
ROLLING – This options loads the updated database by stopping the exiting q process and starting a new q process with updated configuration.
NO_RESTART – This option loads the updated database on the running q process without stopping it. This option is quicker as it reduces the turn around time to update a kdb database changeset configuration on a cluster.
deploymentStrategy - The type of deployment that you want on a cluster.
ROLLING – This options loads the updated database by stopping the exiting q process and starting a new q process with updated configuration.
NO_RESTART – This option loads the updated database on the running q process without stopping it. This option is quicker as it reduces the turn around time to update a kdb database changeset configuration on a cluster.
KxDeploymentStrategy,
KxDeploymentStrategyKxDeploymentConfiguration.Builder deploymentStrategy(KxDeploymentStrategy deploymentStrategy)
The type of deployment that you want on a cluster.
ROLLING – This options loads the updated database by stopping the exiting q process and starting a new q process with updated configuration.
NO_RESTART – This option loads the updated database on the running q process without stopping it. This option is quicker as it reduces the turn around time to update a kdb database changeset configuration on a cluster.
deploymentStrategy - The type of deployment that you want on a cluster.
ROLLING – This options loads the updated database by stopping the exiting q process and starting a new q process with updated configuration.
NO_RESTART – This option loads the updated database on the running q process without stopping it. This option is quicker as it reduces the turn around time to update a kdb database changeset configuration on a cluster.
KxDeploymentStrategy,
KxDeploymentStrategyCopyright © 2023. All rights reserved.