client.rb in aws-sdk-neptunedata-1.5.0

- old
+ new

@@ -1157,11 +1157,11 @@
     # When invoking this operation in a Neptune cluster that has IAM
     # authentication enabled, the IAM user or role making the request must
     # have a policy attached that allows the
     # [neptune-db:ReadDataViaQuery][2] IAM action in that cluster.
     #
-    # Note that the [neptune-db:QueryLanguage:Opencypher][3] IAM condition
+    # Note that the [neptune-db:QueryLanguage:OpenCypher][3] 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][4]).
     #
     #
@@ -1228,11 +1228,11 @@
     #
     # * [neptune-db:WriteDataViaQuery][4]
     #
     # * [neptune-db:DeleteDataViaQuery][5]
     #
-    # Note also that the [neptune-db:QueryLanguage:Opencypher][6] IAM
+    # Note also that the [neptune-db:QueryLanguage:OpenCypher][6] 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][7]).
     #
     #
@@ -1707,11 +1707,11 @@
     # When invoking this operation in a Neptune cluster that has IAM
     # authentication enabled, the IAM user or role making the request must
     # have a policy attached that allows the [neptune-db:GetQueryStatus][1]
     # IAM action in that cluster.
     #
-    # Note that the [neptune-db:QueryLanguage:Opencypher][2] IAM condition
+    # Note that the [neptune-db:QueryLanguage:OpenCypher][2] 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][3]).
     #
     #
@@ -1816,11 +1816,11 @@
     # Note that you can restrict property-graph queries using the following
     # IAM context keys:
     #
     # * [neptune-db:QueryLanguage:Gremlin][4]
     #
-    # * [neptune-db:QueryLanguage:Opencypher][4]
+    # * [neptune-db:QueryLanguage:OpenCypher][4]
     #
     # See [Condition keys available in Neptune IAM data-access policy
     # statements][5]).
     #
     #
@@ -2481,11 +2481,11 @@
     # When invoking this operation in a Neptune cluster that has IAM
     # authentication enabled, the IAM user or role making the request must
     # have a policy attached that allows the [neptune-db:GetQueryStatus][2]
     # IAM action in that cluster.
     #
-    # Note that the [neptune-db:QueryLanguage:Opencypher][3] IAM condition
+    # Note that the [neptune-db:QueryLanguage:OpenCypher][3] 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][4]).
     #
     #
@@ -2832,11 +2832,12 @@
     #   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"`.
+    #   `"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.
     #
     #   *Allowed values*: `"TRUE"`, `"FALSE"`.
@@ -3331,10 +3332,10 @@
         operation: config.api.operation(operation_name),
         client: self,
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-neptunedata'
-      context[:gem_version] = '1.4.0'
+      context[:gem_version] = '1.5.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 
     # @api private
     # @deprecated