Amazon Neptune Engine Updates 2018-06-22 - Amazon Neptune
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Amazon Neptune Engine Updates 2018-06-22

Version: 1.0.1.0.200233.0

Amazon Neptune 1.0.1.0.200233.0 is generally available. All new Neptune DB clusters, including those restored from snapshots, will be created in Neptune 1.0.1.0.200233.0 after the engine update is complete for that Region.

Existing clusters can be upgraded to this release immediately using the DB cluster operations on the console or by using the SDK. You can use the following CLI command to upgrade a DB cluster to this release immediately:

aws neptune apply-pending-maintenance-action \ --apply-action system-update \ --opt-in-type immediate \ --resource-identifier arn:aws-cn:rds:<region>:<account number>:<resourcetype>:<name>

Neptune DB clusters will automatically be upgraded to engine release 1.0.1.0.200233.0 during system maintenance windows. The timing of when updates are applied depends on the Region and maintenance window setting for the DB cluster, as well as on the type of update.

Note

The instance maintenance window does not apply to engine updates.

Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on all instances in a DB cluster, so you will experience downtime ranging from 20–30 seconds to several minutes, after which you can resume using your DB cluster or clusters. You can view or change your maintenance window settings on the Neptune console.

If you have any questions or concerns, the Amazon Support team is available on the community forums and through Amazon Premium Support.

Improvements

  • Fixed an issue where a large number of bulk load requests are issued in quick succession results in an error.

  • Fixed a data-dependent issue where a query could fail with an InternalServerError. The following example shows the type of query affected.

    g.V("my-id123").as("start").outE("knows").has("edgePropertyKey1", P.gt(0)).as("myedge").inV() .as("end").select("start", "end", "myedge").by("vertexPropertyKey1") .by("vertexPropertyKey1").by("edgePropertyKey1")
  • Fixed an issue where a Gremlin Java client cannot connect to the server using the same WebSocket connection after the timeout of a long-running query.

  • Fixed an issue where the escaped sequences contained as part of the Gremlin query over HTTP or string-based queries over the WebSocket connection were not handled correctly.