aws-sdk-neptunedata 1.4.0 → 1.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 71f98fb6c9100b795cee57ef8ea9f18ce6ee3d76abfb9dabbb605b954642588d
-  data.tar.gz: adb55f0246e90296ad37809cbdab7adc889b390ceaba561c4cd55ef183787dc8
+  metadata.gz: 004eaa03e4cb6c2a207a0fc6c180f0bc009657731e725eb6fd4fa0de74ed7223
+  data.tar.gz: 8bd8c7c97a0889b0568195bd545c089a0e0017165a43f3ab9a1fd493e4152d54
 SHA512:
-  metadata.gz: 6a70a2f231c527dd45fa7a78f157c3b373af68c2477257a886f0b8e3e004fd92ca8e9a84acde5463df2b484f2f661ef1d52d7ae2f5501e31ffc95b8f97ae37ca
-  data.tar.gz: 2540809b64a56dbd5f304d3361733590d456d0bae710fc4cf46e0da13163031a4197aaf11e3f8424eeb72f7d1f88ad99e606e788f9500258f1a349ebc5ba65c5
+  metadata.gz: 36de6db2993df3292b3cf29dd00d63d33894a0e9442972e3454bc4076a8992165f9b103f207b62539990641adfa62bca090e23456a1eaaa4dd444ec395110a3e
+  data.tar.gz: cf048c69c94a4d355b68f499da17168d2d7552f811375a33f7c45a8e742877946a5ddc105d8bb8fb80107369aa7904dc05d6c6271ae8b2a3480ba50222f10c8e

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.5.0 (2023-10-31)
+------------------
+
+* Feature - Minor change to not retry CancelledByUserException
+
 1.4.0 (2023-10-19)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.4.0
+1.5.0

data/lib/aws-sdk-neptunedata/client.rb

@@ -1159,7 +1159,7 @@ module Aws::Neptunedata
     # 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]).
@@ -1230,7 +1230,7 @@ module Aws::Neptunedata
     #
     # * [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]).
@@ -1709,7 +1709,7 @@ module Aws::Neptunedata
     # 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]).
@@ -1818,7 +1818,7 @@ module Aws::Neptunedata
     #
     # * [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]).
@@ -2483,7 +2483,7 @@ module Aws::Neptunedata
     # 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]).
@@ -2834,7 +2834,8 @@ module Aws::Neptunedata
     #   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.
@@ -3333,7 +3334,7 @@ module Aws::Neptunedata
         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
 

data/lib/aws-sdk-neptunedata/errors.rb

@@ -170,10 +170,6 @@ module Aws::Neptunedata
       def code
         @code || @data[:code]
       end
-
-      def retryable?
-        true
-      end
     end
 
     class ClientTimeoutException < ServiceError

data/lib/aws-sdk-neptunedata/types.rb

@@ -3248,7 +3248,8 @@ module Aws::Neptunedata
     #   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.

data/lib/aws-sdk-neptunedata.rb

@@ -52,6 +52,6 @@ require_relative 'aws-sdk-neptunedata/customizations'
 # @!group service
 module Aws::Neptunedata
 
-  GEM_VERSION = '1.4.0'
+  GEM_VERSION = '1.5.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-neptunedata
 version: !ruby/object:Gem::Version
-  version: 1.4.0
+  version: 1.5.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-10-19 00:00:00.000000000 Z
+date: 2023-10-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core