From 1c2b78d29a3d5c35bd4739294a1dadd6a2ec9c0f Mon Sep 17 00:00:00 2001 From: awstools Date: Tue, 31 Oct 2023 18:29:50 +0000 Subject: [PATCH] feat(client-neptunedata): Minor change to not retry CancelledByUserException --- .../ExecuteOpenCypherExplainQueryCommand.ts | 2 +- .../commands/ExecuteOpenCypherQueryCommand.ts | 2 +- .../GetOpenCypherQueryStatusCommand.ts | 2 +- .../commands/GetPropertygraphStreamCommand.ts | 2 +- .../commands/ListOpenCypherQueriesCommand.ts | 2 +- .../client-neptunedata/src/models/models_0.ts | 100 +++++++++--------- .../sdk-codegen/aws-models/neptunedata.json | 27 +++-- 7 files changed, 68 insertions(+), 69 deletions(-) diff --git a/clients/client-neptunedata/src/commands/ExecuteOpenCypherExplainQueryCommand.ts b/clients/client-neptunedata/src/commands/ExecuteOpenCypherExplainQueryCommand.ts index a954df7e1c53..9bf1169e9c50 100644 --- a/clients/client-neptunedata/src/commands/ExecuteOpenCypherExplainQueryCommand.ts +++ b/clients/client-neptunedata/src/commands/ExecuteOpenCypherExplainQueryCommand.ts @@ -57,7 +57,7 @@ export interface ExecuteOpenCypherExplainQueryCommandOutput * authentication enabled, the IAM user or role making the request must * have a policy attached that allows the neptune-db:ReadDataViaQuery * IAM action in that cluster.

- *

Note that the neptune-db:QueryLanguage:Opencypher + *

Note that the neptune-db:QueryLanguage:OpenCypher * IAM condition key can be used in the policy document to restrict the use of * openCypher queries (see Condition * keys available in Neptune IAM data-access policy statements).

diff --git a/clients/client-neptunedata/src/commands/ExecuteOpenCypherQueryCommand.ts b/clients/client-neptunedata/src/commands/ExecuteOpenCypherQueryCommand.ts index e117261d525c..ab8b5e6eba7b 100644 --- a/clients/client-neptunedata/src/commands/ExecuteOpenCypherQueryCommand.ts +++ b/clients/client-neptunedata/src/commands/ExecuteOpenCypherQueryCommand.ts @@ -69,7 +69,7 @@ export interface ExecuteOpenCypherQueryCommandOutput extends ExecuteOpenCypherQu *

* * - *

Note also that the neptune-db:QueryLanguage:Opencypher + *

Note also that the neptune-db:QueryLanguage:OpenCypher * IAM condition key can be used in the policy document to restrict the use of * openCypher queries (see Condition * keys available in Neptune IAM data-access policy statements).

diff --git a/clients/client-neptunedata/src/commands/GetOpenCypherQueryStatusCommand.ts b/clients/client-neptunedata/src/commands/GetOpenCypherQueryStatusCommand.ts index 2d326d309e1c..bff296a5e02c 100644 --- a/clients/client-neptunedata/src/commands/GetOpenCypherQueryStatusCommand.ts +++ b/clients/client-neptunedata/src/commands/GetOpenCypherQueryStatusCommand.ts @@ -42,7 +42,7 @@ export interface GetOpenCypherQueryStatusCommandOutput extends GetOpenCypherQuer * authentication enabled, the IAM user or role making the request must * have a policy attached that allows the neptune-db:GetQueryStatus * IAM action in that cluster.

- *

Note that the neptune-db:QueryLanguage:Opencypher + *

Note that the neptune-db:QueryLanguage:OpenCypher * IAM condition key can be used in the policy document to restrict the use of * openCypher queries (see Condition * keys available in Neptune IAM data-access policy statements).

diff --git a/clients/client-neptunedata/src/commands/GetPropertygraphStreamCommand.ts b/clients/client-neptunedata/src/commands/GetPropertygraphStreamCommand.ts index 2a4155ed4ddc..d69f80ee6b00 100644 --- a/clients/client-neptunedata/src/commands/GetPropertygraphStreamCommand.ts +++ b/clients/client-neptunedata/src/commands/GetPropertygraphStreamCommand.ts @@ -65,7 +65,7 @@ export interface GetPropertygraphStreamCommandOutput extends GetPropertygraphStr * *
  • *

    - * neptune-db:QueryLanguage:Opencypher + * neptune-db:QueryLanguage:OpenCypher *

    *
    • * diff --git a/clients/client-neptunedata/src/commands/ListOpenCypherQueriesCommand.ts b/clients/client-neptunedata/src/commands/ListOpenCypherQueriesCommand.ts index a41a21232465..48c8eaac0c20 100644 --- a/clients/client-neptunedata/src/commands/ListOpenCypherQueriesCommand.ts +++ b/clients/client-neptunedata/src/commands/ListOpenCypherQueriesCommand.ts @@ -43,7 +43,7 @@ export interface ListOpenCypherQueriesCommandOutput extends ListOpenCypherQuerie * authentication enabled, the IAM user or role making the request must * have a policy attached that allows the neptune-db:GetQueryStatus * IAM action in that cluster.

    - *

    Note that the neptune-db:QueryLanguage:Opencypher + *

    Note that the neptune-db:QueryLanguage:OpenCypher * IAM condition key can be used in the policy document to restrict the use of * openCypher queries (see Condition * keys available in Neptune IAM data-access policy statements).

    diff --git a/clients/client-neptunedata/src/models/models_0.ts b/clients/client-neptunedata/src/models/models_0.ts index 8237b5ae022e..bb0d52e42f60 100644 --- a/clients/client-neptunedata/src/models/models_0.ts +++ b/clients/client-neptunedata/src/models/models_0.ts @@ -1462,7 +1462,6 @@ export class ServerShutdownException extends __BaseException { export class CancelledByUserException extends __BaseException { readonly name: "CancelledByUserException" = "CancelledByUserException"; readonly $fault: "server" = "server"; - $retryable = {}; /** * @public *

    A detailed message describing the problem.

    @@ -4017,7 +4016,7 @@ export interface StartLoaderJobInput { /** * @public *

    The format of the data. For more information about data formats for the Neptune - * Loader command, see Load Data Formats.

    + * Loader command, see Load Data Formats.

    *

    * Allowed values *

    @@ -4097,14 +4096,14 @@ export interface StartLoaderJobInput { *
  • *

    * RESUME   –   In RESUME mode, - * the loader looks for a previous load from this source, and if it finds - * one, resumes that load job. If no previous load job is found, the loader stops.

    + * the loader looks for a previous load from this source, and if it finds + * one, resumes that load job. If no previous load job is found, the loader stops.

    *

    The loader avoids reloading files that were successfully loaded in - * a previous job. It only tries to process failed files. If you dropped - * previously loaded data from your Neptune cluster, that data is not - * reloaded in this mode. If a previous load job loaded all files from the - * same source successfully, nothing is reloaded, and the loader returns - * success.

    + * a previous job. It only tries to process failed files. If you dropped + * previously loaded data from your Neptune cluster, that data is not + * reloaded in this mode. If a previous load job loaded all files from the + * same source successfully, nothing is reloaded, and the loader returns + * success.

    *
    • *
  • *

    @@ -4117,11 +4116,11 @@ export interface StartLoaderJobInput { *

  • *

    * AUTO   –   In AUTO mode, - * the loader looks for a previous load job from the same source, and if it - * finds one, resumes that job, just as in RESUME mode.

    + * the loader looks for a previous load job from the same source, and if it + * finds one, resumes that job, just as in RESUME mode.

    *

    If the loader doesn't find a previous load job from the same - * source, it loads all data from the source, just as in NEW - * mode.

    + * source, it loads all data from the source, just as in NEW + * mode.

    *
    • * */ @@ -4170,11 +4169,11 @@ export interface StartLoaderJobInput { *
  • *

    * OVERSUBSCRIBE –   The number of threads used is the - * number of available vCPUs multiplied by 2. If this value is used, the bulk loader takes up all - * available resources.

    + * number of available vCPUs multiplied by 2. If this value is used, the bulk loader takes up all + * available resources.

    *

    This does not mean, however, that the OVERSUBSCRIBE setting - * results in 100% CPU utilization. Because the load operation is I/O bound, the - * highest CPU utilization to expect is in the 60% to 70% range.

    + * results in 100% CPU utilization. Because the load operation is I/O bound, the + * highest CPU utilization to expect is in the 60% to 70% range.

    *
    • * *

    @@ -4204,8 +4203,8 @@ export interface StartLoaderJobInput { * * namedGraphUri *   – - * The default graph for all RDF formats when no graph is specified (for non-quads - * formats and NQUAD entries with no graph).

    + * The default graph for all RDF formats when no graph is specified (for non-quads + * formats and NQUAD entries with no graph).

    *

    The default is https://aws.amazon.com/neptune/vocab/v01/DefaultNamedGraph.

    * *
  • @@ -4213,7 +4212,7 @@ export interface StartLoaderJobInput { * * baseUri *   – - * The base URI for RDF/XML and Turtle formats.

    + * The base URI for RDF/XML and Turtle formats.

    *

    The default is https://aws.amazon.com/neptune/default.

    *
    • *
  • @@ -4221,13 +4220,13 @@ export interface StartLoaderJobInput { * * allowEmptyStrings *   – - * Gremlin users need to be able to pass empty string values("") as node - * and edge properties when loading CSV data. If allowEmptyStrings - * is set to false (the default), such empty strings are treated - * as nulls and are not loaded.

    + * Gremlin users need to be able to pass empty string values("") as node + * and edge properties when loading CSV data. If allowEmptyStrings + * is set to false (the default), such empty strings are treated + * as nulls and are not loaded.

    *

    If allowEmptyStrings is set to true, - * the loader treats empty strings as valid property values and loads - * them accordingly.

    + * the loader treats empty strings as valid property values and loads + * them accordingly.

    *
    • * */ @@ -4237,34 +4236,35 @@ export interface StartLoaderJobInput { * @public *

    * updateSingleCardinalityProperties - * is an optional parameter that controls how the bulk loader treats a new - * value for single-cardinality vertex or edge properties. This is not supported for - * loading openCypher data.

    + * is an optional parameter that controls how the bulk loader treats a new + * value for single-cardinality vertex or edge properties. This is not supported for + * loading openCypher data.

    *

    * Allowed values: "TRUE", "FALSE".

    *

    * Default value: "FALSE".

    *

    By default, or when updateSingleCardinalityProperties is explicitly - * set to "FALSE", the loader treats a new value as an error, because it - * violates single cardinality.

    + * set to "FALSE", the loader treats a new value as an error, because it + * violates single cardinality.

    *

    When updateSingleCardinalityProperties is set to "TRUE", - * on the other hand, the bulk loader replaces the existing value with the new one. - * If multiple edge or single-cardinality vertex property values are provided in the - * source file(s) being loaded, the final value at the end of the bulk load could be - * any one of those new values. The loader only guarantees that the existing value - * has been replaced by one of the new ones.

    + * on the other hand, the bulk loader replaces the existing value with the new one. + * If multiple edge or single-cardinality vertex property values are provided in the + * source file(s) being loaded, the final value at the end of the bulk load could be + * any one of those new values. The loader only guarantees that the existing value + * has been replaced by one of the new ones.

    */ updateSingleCardinalityProperties?: boolean; /** * @public *

    This is an optional flag parameter - * that indicates whether the load request can be queued up or not.

    + * that indicates whether the load request can be queued up or not.

    *

    You don't have to wait for one load job to complete before issuing the next one, - * because Neptune can queue up as many as 64 jobs at a time, provided that their - * queueRequest parameters are all set to "TRUE".

    + * because Neptune can queue up as many as 64 jobs at a time, provided that their + * queueRequest parameters are all set to "TRUE". + * The queue order of the jobs will be first-in-first-out (FIFO).

    *

    If the queueRequest parameter is omitted or set to "FALSE", - * the load request will fail if another load job is already running.

    + * the load request will fail if another load job is already running.

    *

    * Allowed values: "TRUE", "FALSE".

    *

    @@ -4307,19 +4307,19 @@ export interface StartLoaderJobInput { /** * @public *

    This parameter is required only when loading openCypher data that contains relationship - * IDs. It must be included and set to True when openCypher relationship IDs - * are explicitly provided in the load data (recommended).

    + * IDs. It must be included and set to True when openCypher relationship IDs + * are explicitly provided in the load data (recommended).

    *

    When userProvidedEdgeIds is absent or set to True, - * an :ID column must be present in every relationship file in the load.

    + * an :ID column must be present in every relationship file in the load.

    *

    When userProvidedEdgeIds is present and set to False, - * relationship files in the load must not contain an - * :ID column. Instead, the Neptune loader automatically generates an - * ID for each relationship.

    + * relationship files in the load must not contain an + * :ID column. Instead, the Neptune loader automatically generates an + * ID for each relationship.

    *

    It's useful to provide relationship IDs explicitly so that the loader can resume - * loading after error in the CSV data have been fixed, without having to reload any - * relationships that have already been loaded. If relationship IDs have not been - * explicitly assigned, the loader cannot resume a failed load if any relationship file - * has had to be corrected, and must instead reload all the relationships.

    + * loading after error in the CSV data have been fixed, without having to reload any + * relationships that have already been loaded. If relationship IDs have not been + * explicitly assigned, the loader cannot resume a failed load if any relationship file + * has had to be corrected, and must instead reload all the relationships.

    */ userProvidedEdgeIds?: boolean; } diff --git a/codegen/sdk-codegen/aws-models/neptunedata.json b/codegen/sdk-codegen/aws-models/neptunedata.json index 5e112656f905..3fdcc76ecd19 100644 --- a/codegen/sdk-codegen/aws-models/neptunedata.json +++ b/codegen/sdk-codegen/aws-models/neptunedata.json @@ -1534,8 +1534,7 @@ "traits": { "smithy.api#documentation": "

    Raised when a user cancelled a request.

    ", "smithy.api#error": "server", - "smithy.api#httpError": 500, - "smithy.api#retryable": {} + "smithy.api#httpError": 500 } }, "com.amazonaws.neptunedata#Classes": { @@ -2730,7 +2729,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Executes an openCypher explain request. See\n The\n openCypher explain feature for more information.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:ReadDataViaQuery\n IAM action in that cluster.

    \n

    Note that the neptune-db:QueryLanguage:Opencypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", + "smithy.api#documentation": "

    Executes an openCypher explain request. See\n The\n openCypher explain feature for more information.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:ReadDataViaQuery\n IAM action in that cluster.

    \n

    Note that the neptune-db:QueryLanguage:OpenCypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", "smithy.api#http": { "method": "POST", "uri": "/opencypher/explain", @@ -2859,7 +2858,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Executes an openCypher query. See Accessing\n the Neptune Graph with openCypher for more information.

    \n

    Neptune supports building graph applications using openCypher,\n which is currently one of the most popular query languages among\n developers working with graph databases. Developers, business analysts,\n and data scientists like openCypher's declarative, SQL-inspired syntax\n because it provides a familiar structure in which to querying property\n graphs.

    \n

    The openCypher language was originally developed by Neo4j, then\n open-sourced in 2015 and contributed to the openCypher project under an Apache\n 2 open-source license.

    \n

    Note that when invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows one of the following IAM actions\n in that cluster, depending on the query:

    \n \n

    Note also that the neptune-db:QueryLanguage:Opencypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", + "smithy.api#documentation": "

    Executes an openCypher query. See Accessing\n the Neptune Graph with openCypher for more information.

    \n

    Neptune supports building graph applications using openCypher,\n which is currently one of the most popular query languages among\n developers working with graph databases. Developers, business analysts,\n and data scientists like openCypher's declarative, SQL-inspired syntax\n because it provides a familiar structure in which to querying property\n graphs.

    \n

    The openCypher language was originally developed by Neo4j, then\n open-sourced in 2015 and contributed to the openCypher project under an Apache\n 2 open-source license.

    \n

    Note that when invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows one of the following IAM actions\n in that cluster, depending on the query:

    \n \n

    Note also that the neptune-db:QueryLanguage:OpenCypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", "smithy.api#http": { "method": "POST", "uri": "/opencypher", @@ -3893,7 +3892,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Retrieves the status of a specified openCypher query.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:GetQueryStatus\n IAM action in that cluster.

    \n

    Note that the neptune-db:QueryLanguage:Opencypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", + "smithy.api#documentation": "

    Retrieves the status of a specified openCypher query.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:GetQueryStatus\n IAM action in that cluster.

    \n

    Note that the neptune-db:QueryLanguage:OpenCypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", "smithy.api#http": { "method": "GET", "uri": "/opencypher/status/{queryId}", @@ -4072,7 +4071,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Gets a stream for a property graph.

    \n

    With the Neptune Streams feature, you can generate a complete\n sequence of change-log entries that record every change made to your\n graph data as it happens. GetPropertygraphStream lets\n you collect these change-log entries for a property graph.

    \n

    The Neptune streams feature needs to be enabled on your Neptune\n DBcluster. To enable streams, set the neptune_streams\n DB cluster parameter to 1.

    \n

    See Capturing\n graph changes in real time using Neptune streams.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:GetStreamRecords\n IAM action in that cluster.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that enables one of the following IAM actions,\n depending on the query:

    \n

    Note that you can restrict property-graph queries using the\n following IAM context keys:

    \n \n

    See Condition\n keys available in Neptune IAM data-access policy statements).

    ", + "smithy.api#documentation": "

    Gets a stream for a property graph.

    \n

    With the Neptune Streams feature, you can generate a complete\n sequence of change-log entries that record every change made to your\n graph data as it happens. GetPropertygraphStream lets\n you collect these change-log entries for a property graph.

    \n

    The Neptune streams feature needs to be enabled on your Neptune\n DBcluster. To enable streams, set the neptune_streams\n DB cluster parameter to 1.

    \n

    See Capturing\n graph changes in real time using Neptune streams.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:GetStreamRecords\n IAM action in that cluster.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that enables one of the following IAM actions,\n depending on the query:

    \n

    Note that you can restrict property-graph queries using the\n following IAM context keys:

    \n \n

    See Condition\n keys available in Neptune IAM data-access policy statements).

    ", "smithy.api#http": { "method": "GET", "uri": "/propertygraph/stream", @@ -5498,7 +5497,7 @@ } ], "traits": { - "smithy.api#documentation": "

    Lists active openCypher queries. See Neptune\n openCypher status endpoint for more information.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:GetQueryStatus\n IAM action in that cluster.

    \n

    Note that the neptune-db:QueryLanguage:Opencypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", + "smithy.api#documentation": "

    Lists active openCypher queries. See Neptune\n openCypher status endpoint for more information.

    \n

    When invoking this operation in a Neptune cluster that has IAM\n authentication enabled, the IAM user or role making the request must\n have a policy attached that allows the neptune-db:GetQueryStatus\n IAM action in that cluster.

    \n

    Note that the neptune-db:QueryLanguage:OpenCypher\n IAM condition key can be used in the policy document to restrict the use of\n openCypher queries (see Condition\n keys available in Neptune IAM data-access policy statements).

    ", "smithy.api#http": { "method": "GET", "uri": "/opencypher/status", @@ -7065,7 +7064,7 @@ "format": { "target": "com.amazonaws.neptunedata#Format", "traits": { - "smithy.api#documentation": "

    The format of the data. For more information about data formats for the Neptune\n Loader command, see Load Data Formats.

    \n

    \n Allowed values\n

    \n ", + "smithy.api#documentation": "

    The format of the data. For more information about data formats for the Neptune\n Loader command, see Load Data Formats.

    \n

    \n Allowed values\n

    \n ", "smithy.api#required": {} } }, @@ -7087,7 +7086,7 @@ "mode": { "target": "com.amazonaws.neptunedata#Mode", "traits": { - "smithy.api#documentation": "

    The load job mode.

    \n

    \n Allowed values: RESUME, NEW,\n AUTO.

    \n

    \n Default value: AUTO.

    \n

    \n \n

    \n " + "smithy.api#documentation": "

    The load job mode.

    \n

    \n Allowed values: RESUME, NEW,\n AUTO.

    \n

    \n Default value: AUTO.

    \n

    \n \n

    \n
      \n
    • \n

      \n RESUME   –   In RESUME mode,\n the loader looks for a previous load from this source, and if it finds\n one, resumes that load job. If no previous load job is found, the loader stops.

      \n

      The loader avoids reloading files that were successfully loaded in\n a previous job. It only tries to process failed files. If you dropped\n previously loaded data from your Neptune cluster, that data is not\n reloaded in this mode. If a previous load job loaded all files from the\n same source successfully, nothing is reloaded, and the loader returns\n success.

      \n
      • \n
    • \n

      \n NEW   –   In NEW mode, the\n creates a new load request regardless of any previous loads. You\n can use this mode to reload all the data from a source after dropping\n previously loaded data from your Neptune cluster, or to load new data\n available at the same source.

      \n
      • \n
    • \n

      \n AUTO   –   In AUTO mode,\n the loader looks for a previous load job from the same source, and if it\n finds one, resumes that job, just as in RESUME mode.

      \n

      If the loader doesn't find a previous load job from the same\n source, it loads all data from the source, just as in NEW\n mode.

      \n
      • \n
    " } }, "failOnError": { @@ -7099,25 +7098,25 @@ "parallelism": { "target": "com.amazonaws.neptunedata#Parallelism", "traits": { - "smithy.api#documentation": "

    The optional parallelism parameter can be set\n to reduce the number of threads used by the bulk load process.

    \n

    \n Allowed values:

    \n
      \n
    • \n

      \n LOW –   The number of threads used is the\n number of available vCPUs divided by 8.

      \n
      • \n
    • \n

      \n MEDIUM –   The number of threads used is the\n number of available vCPUs divided by 2.

      \n
      • \n
    • \n

      \n HIGH –   The number of threads used is the\n same as the number of available vCPUs.

      \n
      • \n
    • \n

      \n OVERSUBSCRIBE –   The number of threads used is the\n number of available vCPUs multiplied by 2. If this value is used, the bulk loader takes up all\n available resources.

      \n

      This does not mean, however, that the OVERSUBSCRIBE setting\n results in 100% CPU utilization. Because the load operation is I/O bound, the\n highest CPU utilization to expect is in the 60% to 70% range.

      \n
      • \n
    \n

    \n Default value: HIGH\n

    \n

    The parallelism setting can sometimes result in a deadlock\n between threads when loading openCypher data. When this happens, Neptune returns the\n LOAD_DATA_DEADLOCK error. You can generally fix the issue by setting\n parallelism to a lower setting and retrying the load command.

    " + "smithy.api#documentation": "

    The optional parallelism parameter can be set\n to reduce the number of threads used by the bulk load process.

    \n

    \n Allowed values:

    \n
      \n
    • \n

      \n LOW –   The number of threads used is the\n number of available vCPUs divided by 8.

      \n
      • \n
    • \n

      \n MEDIUM –   The number of threads used is the\n number of available vCPUs divided by 2.

      \n
      • \n
    • \n

      \n HIGH –   The number of threads used is the\n same as the number of available vCPUs.

      \n
      • \n
    • \n

      \n OVERSUBSCRIBE –   The number of threads used is the\n number of available vCPUs multiplied by 2. If this value is used, the bulk loader takes up all\n available resources.

      \n

      This does not mean, however, that the OVERSUBSCRIBE setting\n results in 100% CPU utilization. Because the load operation is I/O bound, the\n highest CPU utilization to expect is in the 60% to 70% range.

      \n
      • \n
    \n

    \n Default value: HIGH\n

    \n

    The parallelism setting can sometimes result in a deadlock\n between threads when loading openCypher data. When this happens, Neptune returns the\n LOAD_DATA_DEADLOCK error. You can generally fix the issue by setting\n parallelism to a lower setting and retrying the load command.

    " } }, "parserConfiguration": { "target": "com.amazonaws.neptunedata#StringValuedMap", "traits": { - "smithy.api#documentation": "

    \n \n parserConfiguration\n  \n –   An optional object with additional parser configuration values.\n Each of the child parameters is also optional:

    \n

    \n \n

    \n
      \n
    • \n

      \n \n namedGraphUri\n   –  \n The default graph for all RDF formats when no graph is specified (for non-quads\n formats and NQUAD entries with no graph).

      \n

      The default is https://aws.amazon.com/neptune/vocab/v01/DefaultNamedGraph.

      \n
      • \n
    • \n

      \n \n baseUri\n   –  \n The base URI for RDF/XML and Turtle formats.

      \n

      The default is https://aws.amazon.com/neptune/default.

      \n
      • \n
    • \n

      \n \n allowEmptyStrings\n   –  \n Gremlin users need to be able to pass empty string values(\"\") as node\n and edge properties when loading CSV data. If allowEmptyStrings\n is set to false (the default), such empty strings are treated\n as nulls and are not loaded.

      \n

      If allowEmptyStrings is set to true,\n the loader treats empty strings as valid property values and loads\n them accordingly.

      \n
      • \n
    " + "smithy.api#documentation": "

    \n \n parserConfiguration\n  \n –   An optional object with additional parser configuration values.\n Each of the child parameters is also optional:

    \n

    \n \n

    \n
      \n
    • \n

      \n \n namedGraphUri\n   –  \n The default graph for all RDF formats when no graph is specified (for non-quads\n formats and NQUAD entries with no graph).

      \n

      The default is https://aws.amazon.com/neptune/vocab/v01/DefaultNamedGraph.

      \n
      • \n
    • \n

      \n \n baseUri\n   –  \n The base URI for RDF/XML and Turtle formats.

      \n

      The default is https://aws.amazon.com/neptune/default.

      \n
      • \n
    • \n

      \n \n allowEmptyStrings\n   –  \n Gremlin users need to be able to pass empty string values(\"\") as node\n and edge properties when loading CSV data. If allowEmptyStrings\n is set to false (the default), such empty strings are treated\n as nulls and are not loaded.

      \n

      If allowEmptyStrings is set to true,\n the loader treats empty strings as valid property values and loads\n them accordingly.

      \n
      • \n
    " } }, "updateSingleCardinalityProperties": { "target": "smithy.api#Boolean", "traits": { - "smithy.api#documentation": "

    \n updateSingleCardinalityProperties\n is an optional parameter that controls how the bulk loader treats a new\n value for single-cardinality vertex or edge properties. This is not supported for\n loading openCypher data.

    \n

    \n Allowed values: \"TRUE\", \"FALSE\".

    \n

    \n Default value: \"FALSE\".

    \n

    By default, or when updateSingleCardinalityProperties is explicitly\n set to \"FALSE\", the loader treats a new value as an error, because it\n violates single cardinality.

    \n

    When updateSingleCardinalityProperties is set to \"TRUE\",\n on the other hand, the bulk loader replaces the existing value with the new one.\n If multiple edge or single-cardinality vertex property values are provided in the\n source file(s) being loaded, the final value at the end of the bulk load could be\n any one of those new values. The loader only guarantees that the existing value\n has been replaced by one of the new ones.

    " + "smithy.api#documentation": "

    \n updateSingleCardinalityProperties\n is an optional parameter that controls how the bulk loader treats a new\n value for single-cardinality vertex or edge properties. This is not supported for\n loading openCypher data.

    \n

    \n Allowed values: \"TRUE\", \"FALSE\".

    \n

    \n Default value: \"FALSE\".

    \n

    By default, or when updateSingleCardinalityProperties is explicitly\n set to \"FALSE\", the loader treats a new value as an error, because it\n violates single cardinality.

    \n

    When updateSingleCardinalityProperties is set to \"TRUE\",\n on the other hand, the bulk loader replaces the existing value with the new one.\n If multiple edge or single-cardinality vertex property values are provided in the\n source file(s) being loaded, the final value at the end of the bulk load could be\n any one of those new values. The loader only guarantees that the existing value\n has been replaced by one of the new ones.

    " } }, "queueRequest": { "target": "smithy.api#Boolean", "traits": { - "smithy.api#documentation": "

    This is an optional flag parameter\n that indicates whether the load request can be queued up or not.

    \n

    You don't have to wait for one load job to complete before issuing the next one,\n because Neptune can queue up as many as 64 jobs at a time, provided that their\n queueRequest parameters are all set to \"TRUE\".

    \n

    If the queueRequest parameter is omitted or set to \"FALSE\",\n the load request will fail if another load job is already running.

    \n

    \n Allowed values: \"TRUE\", \"FALSE\".

    \n

    \n Default value: \"FALSE\".

    " + "smithy.api#documentation": "

    This is an optional flag parameter\n that indicates whether the load request can be queued up or not.

    \n

    You don't have to wait for one load job to complete before issuing the next one,\n because Neptune can queue up as many as 64 jobs at a time, provided that their\n queueRequest parameters are all set to \"TRUE\".\n The queue order of the jobs will be first-in-first-out (FIFO).

    \n

    If the queueRequest parameter is omitted or set to \"FALSE\",\n the load request will fail if another load job is already running.

    \n

    \n Allowed values: \"TRUE\", \"FALSE\".

    \n

    \n Default value: \"FALSE\".

    " } }, "dependencies": { @@ -7129,7 +7128,7 @@ "userProvidedEdgeIds": { "target": "smithy.api#Boolean", "traits": { - "smithy.api#documentation": "

    This parameter is required only when loading openCypher data that contains relationship\n IDs. It must be included and set to True when openCypher relationship IDs\n are explicitly provided in the load data (recommended).

    \n

    When userProvidedEdgeIds is absent or set to True,\n an :ID column must be present in every relationship file in the load.

    \n

    When userProvidedEdgeIds is present and set to False,\n relationship files in the load must not contain an\n :ID column. Instead, the Neptune loader automatically generates an\n ID for each relationship.

    \n

    It's useful to provide relationship IDs explicitly so that the loader can resume\n loading after error in the CSV data have been fixed, without having to reload any\n relationships that have already been loaded. If relationship IDs have not been\n explicitly assigned, the loader cannot resume a failed load if any relationship file\n has had to be corrected, and must instead reload all the relationships.

    " + "smithy.api#documentation": "

    This parameter is required only when loading openCypher data that contains relationship\n IDs. It must be included and set to True when openCypher relationship IDs\n are explicitly provided in the load data (recommended).

    \n

    When userProvidedEdgeIds is absent or set to True,\n an :ID column must be present in every relationship file in the load.

    \n

    When userProvidedEdgeIds is present and set to False,\n relationship files in the load must not contain an\n :ID column. Instead, the Neptune loader automatically generates an\n ID for each relationship.

    \n

    It's useful to provide relationship IDs explicitly so that the loader can resume\n loading after error in the CSV data have been fixed, without having to reload any\n relationships that have already been loaded. If relationship IDs have not been\n explicitly assigned, the loader cannot resume a failed load if any relationship file\n has had to be corrected, and must instead reload all the relationships.

    " } } },