Amazon Neptune Engine Version (2020-07-23) - 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-07-23)

As of 2020-07-23, 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 memory usage by releasing unused memory back to the operating system more frequently.

  • Also improved memory usage for SPARQL GROUP BY queries.

  • Increased the maximum time a WebSocket connection can stay open that is authenticated using IAM, from 36 hours to 10 days.

  • Added the BufferCacheHitRatio CloudWatch metric, which can be useful in diagnosing query latency and tuning instance types. See Neptune Metrics.

Defects Fixed in This Engine Release

  • Fixed a bug in closing idle or expired IAM WebSocket connections. Neptune now sends a close frame before closing the connection.

  • Fixed a SPARQL bug in the evaluation of queries containing nested FILTER EXISTS and/or FILTER NOT EXISTS conditions.

  • Fixed a SPARQL query termination bug that caused blocked threads on the server under certain extreme conditions.

  • Fixed a Gremlin bug involving Edge pathType in the hasLabel step.

  • Fixed a Gremlin bug to handle toV and fromV individually for each direction on bothE.

  • Fixed a Gremlin bug involving disappearing sideEffects.

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

Your cluster will be upgraded to this patch release automatically during your next maintenance window if you are running engine version

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

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.