Amazon Neptune Engine Version (2020-10-12) - 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 Version (2020-10-12)

As of 2020-10-12, engine version is being generally deployed. Please note that it takes several days for a new release to become available in every region.

Improvements in This Engine Release

  • Improved performance for the Gremlin properties() step.

  • Added details about BindOp and MultiplexerOp in explain and profile reports.

  • For SPARQL query responses, added charset to the Content-Type header, enabling HTTP clients to recognize the charset being used automatically.

Defects Fixed in This Engine Release

  • Fixed a SPARQL bug where CancellationException was not handled.

  • Fixed a SPARQL bug where queries containing nested optionals did not work correctly.

  • Fixed a SPARQL bug in LOAD where a ConcurrentModificationException could cause a query to hang.

  • Fixed a SPARQL bug that prevented query responses from being gzip-compressed.

  • Fixed a Gremlin bug in the groupBy() step.

  • Fixed a Gremlin bug related to the use of an aggregate() step inside a local() step.

  • Fixed a Gremlin bug related to using bothE() followed by a predicate that uses aggregate values.

  • Fixed a Gremlin bug related to using the bothE() step with the repeat() step.

  • Fixed a potential Gremlin memory leak related to the both() step.

  • Fixed a bug where request metrics were missing because an endpoint ending in '/' was not being handled correctly.

  • Fixed a bug that could raise a ThrottlingException even when the request queue is not full.

  • Fixed a bug in fetching load status when a load fails for a reason such as LOAD_DATA_FAILED_DUE_TO_FEED_MODIFIED_OR_DELETE.

Query-Language Versions Supported in This Release

Before upgrading a DB cluster to version, make sure that your project is compatible with these query-language versions:

  • Gremlin version: 3.4.3

  • SPARQL version: 1.1

Upgrade Paths to Engine Release

You can manually upgrade any previous Neptune engine release to this release.

If your cluster has its AutoMinorVersionUpgrade parameter set to True, your cluster will be upgraded to this engine release automatically two to three weeks after the date of this release, during a maintenance window.

Upgrading to This Release

Amazon Neptune is now generally available.

If a DB cluster is running an engine version from which there is an upgrade path to this release, it is eligible to be upgraded now. You can upgrade any eligible cluster using the DB cluster operations on the console or by using the SDK. The following CLI command will upgrade an eligible cluster immediately:

For Linux, OS X, or Unix:

aws neptune modify-db-cluster \ --db-cluster-identifier (your-neptune-cluster) \ --engine-version \ --apply-immediately

For Windows:

aws neptune modify-db-cluster ^ --db-cluster-identifier (your-neptune-cluster) ^ --engine-version ^ --apply-immediately

Updates are applied to all instances in a DB cluster simultaneously. An update requires a database restart on those instances, so you will experience downtime ranging from 20–30 seconds to several minutes, after which you can resume using the DB cluster.

For more information about upgrading your engine version, see Neptune engine updates. If you have any questions or concerns, the Amazon Support team is available on the community forums and through Amazon Premium Support.