Amazon Neptune Engine Version 1.0.2.1.R4 (2019-12-20) - Amazon Neptune

Amazon Neptune Engine Version 1.0.2.1.R4 (2019-12-20)

Improvements in This Engine Release

  • Neptune now tries always to place any full-text-search call first in the execution pipeline. This reduces the volume of calls to Elasticsearch, which can significantly improve performance. See Full-Text-Search Query Execution.

  • Neptune now raises an IllegalArgumentException if you try to access a non-existent property, vertex, or edge. Previously, Neptune raised an UnsupportedOperationException in that situation.

    For example, if you try to add an edge referencing a nonexistent vertex, you will now raise an IllegalArgumentException.

Defects Fixed in This Engine Release

  • Fixed a Gremlin bug where a union traversal inside a project-by does not return results or returns incorrect results.

  • Fixed a Gremlin bug that caused nested .project().by() steps to return incorrect results.

Query-Language Versions Supported in This Release

Before upgrading a DB cluster to version 1.0.2.1.R4, 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 1.0.2.1.R4

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 1.0.2.1.R4 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.2.1 \ --apply-immediately

For Windows:

aws neptune modify-db-cluster ^ --db-cluster-identifier <your-neptune-cluster> ^ --engine-version 1.0.2.1 ^ --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 AWS Support team is available on the community forums and through AWS Premium Support.