Amazon Neptune Engine Updates 2019-08-13 - Amazon Neptune

Amazon Neptune Engine Updates 2019-08-13


Amazon Neptune is generally available. All new Neptune DB clusters, including those restored from snapshots, will be created in Neptune 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: because release can introduce breaking changes for some customers, upgrades will NOT occur automatically during the system maintenance window. If you want to upgrade a DB cluster to, use the CLI command above to upgrade manually.

New Features in This Engine Release

  • Added an OVERSUBSCRIBE option to the parallelism parameter of the Neptune Loader Command, which causes the Neptune bulk loader to use all available threads and resources.

Improvements in This Engine Release

  • Improved performance of SPARQL filters containing simple logical OR expressions.

  • Improved Gremlin performance in handling conjunctive predicates.

Defects Fixed in This Engine Release

  • Fixed a SPARQL bug preventing subtraction of an an xsd:duration from an xsd:date.

  • Fixed a SPARQL bug causing incomplete results from static inlining in the presence of a UNION.

  • Fixed a SPARQL bug in query cancellation.

  • Fixed a Gremlin bug causing overflow during type promotion.

  • Fixed a Gremlin bug in the handling of vertex elements in addE().from().to() steps.

  • Fixed a Gremlin bug (released 2019-07-26 in Engine version involving the handling of NaN doubles and floats in single-cardinality inserts.

  • Fixed a bug in generating query plans involving property based searches.