Amazon Neptune Engine Version (2020-04-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 Version (2020-04-22)

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

Defects Fixed in This Engine Release

  • Fixed a bug where ConcurrentModificationConflictException and TransactionException were not converted into a NeptuneGremlinException, causing InternalFailureException to be returned to customers.

  • Fixed a bug where Neptune reported its status as healthy before the server was completely ready.

  • Fixed a bug where dictionary and user transaction commits were out of order when two value->id mappings were being inserted concurrently.

  • Fixed a bug in load-status serialization.

  • Fixed a Gremlin sessions bug.

  • Fixed a bug where Neptune failed to throw an exception when the server failed to start.

  • Fixed a bug where Neptune failed to send a Web socket close frame before closing the channel.

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.1

  • 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.