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

Defects Fixed in This Engine Release

  • Fixed a bug where the OSGP index was disabled even though the feature was correctly enabled using inLab Mode using the ObjectIndex value in the neptune_lab_mode parameter.

  • Fixed a bug that affected Gremlin queries with a .fold() inside a .project().by() step. For example, it caused the following query to return incomplete results:

  • Fixed a performance bottleneck in bulk loads of RDF data.

  • Fixed a bug that caused a crash on replicas when streams were enabled and the replica was restarted before the primary.

  • Fixed a bug where rotated SSL certificates on instances were not picked up without an instance restart.

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

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

However, automatic updating to this release is not supported.

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.