Amazon Neptune Engine Updates 2019-10-31 - Amazon Neptune

Amazon Neptune Engine Updates 2019-10-31

Version: 1.0.1.0.200502.0

Important

Engine release 1.0.1.0.200502.0 and earlier versions are not available in the AWS ARN region.

As of today, Amazon Neptune 1.0.1.0.200502.0 is being deployed to all regions. All new Neptune DB clusters, including those restored from snapshots, will be created in Neptune 1.0.1.0.200502.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:

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

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 AWS Support team is available on the community forums and through AWS Premium Support.

IMPORTANT: upgrades to release 1.0.1.0.200502.0 will NOT occur automatically during the system maintenance window.

If you want to upgrade a DB cluster to 1.0.1.0.200502.0, use the CLI command above to upgrade manually.

Defects Fixed in This Engine Release

  • Fixed a Gremlin bug in the serialization of the tree() step's response when clients connect to Neptune using traversal().withRemote(...) (in other words, using GLV bytecode).

    This release addresses an issue in which clients who connected to Neptune using traversal().withRemote(...) received an invalid response to Gremlin queries that contained a tree() step.

  • Fixed a SPARQL bug in DELETE WHERE LIMIT queries, in which the query termination process would hang because of a race condition, causing the query to time out.