Amazon Neptune Engine Version 1.0.3.0.R3 (2021-02-19) - 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 1.0.3.0.R3 (2021-02-19)

As of 2021-02-19, engine version 1.0.3.0.R3 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 in the CSV bulk load involving labels that end in #.

  • Fixed a Gremlin bug that could cause missing results for a specific pattern of queries that use the as() step.

  • Fixed a Gremlin bug that could cause errors when using the project() step nested inside another step such as union().

  • Fixed a Gremlin bug in string traversal execution in the experimental DFE engine when a terminal method like toList() is used.

  • Fixed a Gremlin bug that fails to close a transaction when using the iterate() step in a string query.

  • Fixed a Gremlin bug that could cause queries using the is(P.gte(0)) pattern to throw an exception under certain conditions.

  • Fixed a Gremlin bug where InternalFailureException was set as the response code in certain circumstances when a ConcurrentModificationException occurred.

  • Fixed a Gremlin bug where under certain conditions updating edges or vertices could cause a transient InternalFailureException.

Query-Language Versions Supported in This Release

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

  • Gremlin version: 3.4.8

  • SPARQL version: 1.1

Upgrade Paths to Engine Release 1.0.3.0.R3

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

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

Upgrading to This Release

Amazon Neptune 1.0.3.0.R3 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 1.0.3.0 \ --apply-immediately

For Windows:

aws neptune modify-db-cluster ^ --db-cluster-identifier (your-neptune-cluster) ^ --engine-version 1.0.3.0 ^ --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.