From 38c6f75e4f8920ff662d98d7093a2ef7c932f37d Mon Sep 17 00:00:00 2001
From: awstools Enables on-demand caching on the selected database path when a particular file or a
+ * column of the database is accessed. When on demand caching is True, dataviews perform minimal loading of files on the filesystem as
+ * needed. When it is set to False, everything is cached. The
+ * default value is False. The number of availability zones you want to assign per cluster. This can be one of the following
- *
- * The number of availability zones you want to assign per volume. Currently, FinSpace only supports
+ * The option to specify whether you want to make the dataview writable to perform database maintenance. The following are some considerations related to writable dataviews.
You cannot create partial writable dataviews. When you create writeable dataviews you must
+ * provide the entire database path. You cannot perform updates on a writeable dataview. Hence, You must also use a unique volume for creating a writeable dataview. So, if you choose a
+ * volume that is already in use by another dataview, the dataview creation
+ * fails. Once you create a dataview as writeable, you cannot change it to read-only. So, you cannot
+ * update the A description of the dataview. The number of availability zones you want to assign per cluster. This can be one of the following
- *
- * The number of availability zones you want to assign per volume. Currently, FinSpace only supports Returns True if the dataview is created as writeable and False otherwise.
* The timestamp at which the dataview was created in FinSpace. The value is determined as epoch time in milliseconds. For example, the value for Monday, November 1, 2021 12:00:00 PM UTC is specified as 1635768000000.
- * The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.
- *
- *
- *
+ * SINGLE
– Assigns one availability zone per cluster.MULTI
– Assigns all the availability zones per cluster.SINGLE
for volumes. This places dataview in a single AZ.
+ *
+ * @public
+ */
+ readWrite?: boolean;
+
/**
* autoUpdate
must be set
+ * as False if readWrite
is True for a dataview.readWrite
parameter later.
- *
+ * SINGLE
– Assigns one availability zone per cluster.MULTI
– Assigns all the availability zones per cluster.SINGLE
for volumes. This places dataview in a single AZ.
You can add one of the following values:
+ *
+ * kx.sg.4xlarge
– The host type with a configuration of 108 GiB memory and 16 vCPUs.
+ * kx.sg.8xlarge
– The host type with a configuration of 216 GiB memory and 32 vCPUs.
+ * kx.sg.16xlarge
– The host type with a configuration of 432 GiB memory and 64 vCPUs.
+ * kx.sg.32xlarge
– The host type with a configuration of 864 GiB memory and 128 vCPUs.
+ * kx.sg1.16xlarge
– The host type with a configuration of 1949 GiB memory and 64 vCPUs.
+ * kx.sg1.24xlarge
– The host type with a configuration of 2948 GiB memory and 96 vCPUs.
The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
- *
- * SINGLE
– Assigns one availability zone per cluster.
- * MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
Returns True if the dataview is created as writeable and False otherwise.
+ * @public + */ + readWrite?: boolean; + /** *A unique identifier for the kdb environment, from where you want to retrieve the dataview details.
* @public @@ -3705,9 +3747,34 @@ export interface GetKxScalingGroupResponse { /** *- * The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed. - * - *
+ * The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed. + *It can have one of the following values:
+ *
+ * kx.sg.4xlarge
– The host type with a configuration of 108 GiB memory and 16 vCPUs.
+ * kx.sg.8xlarge
– The host type with a configuration of 216 GiB memory and 32 vCPUs.
+ * kx.sg.16xlarge
– The host type with a configuration of 432 GiB memory and 64 vCPUs.
+ * kx.sg.32xlarge
– The host type with a configuration of 864 GiB memory and 128 vCPUs.
+ * kx.sg1.16xlarge
– The host type with a configuration of 1949 GiB memory and 64 vCPUs.
+ * kx.sg1.24xlarge
– The host type with a configuration of 2948 GiB memory and 96 vCPUs.
The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
- *
- * SINGLE
– Assigns one availability zone per cluster.
- * MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
Returns True if the dataview is created as writeable and False otherwise.
+ * @public + */ + readWrite?: boolean; + /** ** The timestamp at which the dataview list entry was created in FinSpace. The value is determined as epoch time in milliseconds. For example, the value for Monday, November 1, 2021 12:00:00 PM UTC is specified as 1635768000000.
@@ -4881,9 +4944,34 @@ export interface KxScalingGroup { /** *- * The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed. - * - *
+ * The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed. + *You can add one of the following values:
+ *
+ * kx.sg.4xlarge
– The host type with a configuration of 108 GiB memory and 16 vCPUs.
+ * kx.sg.8xlarge
– The host type with a configuration of 216 GiB memory and 32 vCPUs.
+ * kx.sg.16xlarge
– The host type with a configuration of 432 GiB memory and 64 vCPUs.
+ * kx.sg.32xlarge
– The host type with a configuration of 864 GiB memory and 128 vCPUs.
+ * kx.sg1.16xlarge
– The host type with a configuration of 1949 GiB memory and 64 vCPUs.
+ * kx.sg1.24xlarge
– The host type with a configuration of 2948 GiB memory and 96 vCPUs.
- * The number of availability zones assigned to the volume. Currently, only SINGLE
is supported.
- *
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
- *
- * SINGLE
– Assigns one availability zone per cluster.
- * MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
Returns True if the dataview is created as writeable and False otherwise.
+ * @public + */ + readWrite?: boolean; + /** *A description of the dataview.
* @public @@ -6197,7 +6279,7 @@ export interface UpdateKxVolumeResponse { createdTimestamp?: Date; /** - *The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
\n\n SINGLE
– Assigns one availability zone per cluster.
\n MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The option to specify whether you want to apply all the future additions and corrections automatically to the dataview, when you ingest new changesets. The default value is false.
" } }, + "readWrite": { + "target": "com.amazonaws.finspace#booleanValue", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "\n The option to specify whether you want to make the dataview writable to perform database maintenance. The following are some considerations related to writable dataviews.\u2028\u2028
\nYou cannot create partial writable dataviews. When you create writeable dataviews you must\n provide the entire database path.
\nYou cannot perform updates on a writeable dataview. Hence, autoUpdate
must be set\n as False if readWrite
is True for a dataview.
You must also use a unique volume for creating a writeable dataview. So, if you choose a\n volume that is already in use by another dataview, the dataview creation\n fails.
\nOnce you create a dataview as writeable, you cannot change it to read-only. So, you cannot\n update the readWrite
parameter later.
The number of availability zones you want to assign per cluster. This can be one of the following
\n\n SINGLE
– Assigns one availability zone per cluster.
\n MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The option to select whether you want to apply all the future additions and corrections automatically to the dataview when you ingest new changesets. The default value is false.
" } }, + "readWrite": { + "target": "com.amazonaws.finspace#booleanValue", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "Returns True if the dataview is created as writeable and False otherwise.
" + } + }, "createdTimestamp": { "target": "com.amazonaws.finspace#Timestamp", "traits": { @@ -2312,7 +2334,7 @@ "hostType": { "target": "com.amazonaws.finspace#KxHostType", "traits": { - "smithy.api#documentation": "\n The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.\n \n
", + "smithy.api#documentation": "\n The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.
\nYou can add one of the following values:
\n\n kx.sg.4xlarge
– The host type with a configuration of 108 GiB memory and 16 vCPUs.
\n kx.sg.8xlarge
– The host type with a configuration of 216 GiB memory and 32 vCPUs.
\n kx.sg.16xlarge
– The host type with a configuration of 432 GiB memory and 64 vCPUs.
\n kx.sg.32xlarge
– The host type with a configuration of 864 GiB memory and 128 vCPUs.
\n kx.sg1.16xlarge
– The host type with a configuration of 1949 GiB memory and 64 vCPUs.
\n kx.sg1.24xlarge
– The host type with a configuration of 2948 GiB memory and 96 vCPUs.
The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
\n\n SINGLE
– Assigns one availability zone per cluster.
\n MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The option to specify whether you want to apply all the future additions and corrections automatically to the dataview when new changesets are ingested. The default value is false.
" } }, + "readWrite": { + "target": "com.amazonaws.finspace#booleanValue", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "Returns True if the dataview is created as writeable and False otherwise.
" + } + }, "environmentId": { "target": "com.amazonaws.finspace#EnvironmentId", "traits": { @@ -4794,7 +4823,7 @@ "hostType": { "target": "com.amazonaws.finspace#KxHostType", "traits": { - "smithy.api#documentation": "\n The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.\n \n
" + "smithy.api#documentation": "\n The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.
\nIt can have one of the following values:
\n\n kx.sg.4xlarge
– The host type with a configuration of 108 GiB memory and 16 vCPUs.
\n kx.sg.8xlarge
– The host type with a configuration of 216 GiB memory and 32 vCPUs.
\n kx.sg.16xlarge
– The host type with a configuration of 432 GiB memory and 64 vCPUs.
\n kx.sg.32xlarge
– The host type with a configuration of 864 GiB memory and 128 vCPUs.
\n kx.sg1.16xlarge
– The host type with a configuration of 1949 GiB memory and 64 vCPUs.
\n kx.sg1.24xlarge
– The host type with a configuration of 2948 GiB memory and 96 vCPUs.
The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
\n\n SINGLE
– Assigns one availability zone per cluster.
\n MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
\n The option to specify whether you want to apply all the future additions and corrections automatically to the dataview when you ingest new changesets. The default value is false.\n
" } }, + "readWrite": { + "target": "com.amazonaws.finspace#booleanValue", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "Returns True if the dataview is created as writeable and False otherwise.
" + } + }, "createdTimestamp": { "target": "com.amazonaws.finspace#Timestamp", "traits": { @@ -5933,6 +5969,13 @@ "smithy.api#documentation": "\nThe name of the volume where you want to add data.
", "smithy.api#required": {} } + }, + "onDemand": { + "target": "com.amazonaws.finspace#booleanValue", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "Enables on-demand caching on the selected database path when a particular file or a\n column of the database is accessed. When on demand caching is True, dataviews perform minimal loading of files on the filesystem as\n needed. When it is set to False, everything is cached. The\n default value is False.
" + } } }, "traits": { @@ -6204,8 +6247,7 @@ "type": "integer", "traits": { "smithy.api#range": { - "min": 1200, - "max": 33600 + "min": 1200 } } }, @@ -6322,7 +6364,7 @@ "hostType": { "target": "com.amazonaws.finspace#KxHostType", "traits": { - "smithy.api#documentation": "\n The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.\n \n
" + "smithy.api#documentation": "\n The memory and CPU capabilities of the scaling group host on which FinSpace Managed kdb clusters will be placed.
\nYou can add one of the following values:
\n\n kx.sg.4xlarge
– The host type with a configuration of 108 GiB memory and 16 vCPUs.
\n kx.sg.8xlarge
– The host type with a configuration of 216 GiB memory and 32 vCPUs.
\n kx.sg.16xlarge
– The host type with a configuration of 432 GiB memory and 64 vCPUs.
\n kx.sg.32xlarge
– The host type with a configuration of 864 GiB memory and 128 vCPUs.
\n kx.sg1.16xlarge
– The host type with a configuration of 1949 GiB memory and 64 vCPUs.
\n kx.sg1.24xlarge
– The host type with a configuration of 2948 GiB memory and 96 vCPUs.
\nThe number of availability zones assigned to the volume. Currently, only SINGLE
is supported.\n
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The number of availability zones you want to assign per cluster. This can be one of the following
\n\n SINGLE
– Assigns one availability zone per cluster.
\n MULTI
– Assigns all the availability zones per cluster.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.
The option to specify whether you want to apply all the future additions and corrections automatically to the dataview when new changesets are ingested. The default value is false.
" } }, + "readWrite": { + "target": "com.amazonaws.finspace#booleanValue", + "traits": { + "smithy.api#default": false, + "smithy.api#documentation": "Returns True if the dataview is created as writeable and False otherwise.
" + } + }, "description": { "target": "com.amazonaws.finspace#Description", "traits": { @@ -9488,7 +9537,7 @@ "azMode": { "target": "com.amazonaws.finspace#KxAzMode", "traits": { - "smithy.api#documentation": "The number of availability zones you want to assign per cluster. Currently, FinSpace only support SINGLE
for volumes.
The number of availability zones you want to assign per volume. Currently, FinSpace only supports SINGLE
for volumes. This places dataview in a single AZ.