Amazon Neptune Engine Version (2021-10-01) - 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 (2021-10-01)

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

Subsequent Patch Releases for This Release

New Features in This Engine Release

  • Added a results cache for caching the results of specified queries.

  • Added Date/time support in Neptune openCypher.

  • Added support for List and Map access to elements in Neptune openCypher.

Improvements in This Engine Release

  • Made Neptune openCypher endpoint names case-insensitive.

  • Improved openCypher explain.

  • Improved Gremlin single upsert query patterns terminating with iterate() and profile() steps.

  • Improved performance in Gremlin keys() and property() functions.

  • The Gremlin dedup() step is run in the DFE when it is used with global scope.

  • The following Gremlin HAS predicates are run in the DFE engine when the DFE engine is enabled:

    • EQ

    • NEQ

    • LT

    • LTE

    • GT

    • GTE


    • INSIDE


    • WITHIN

    • AND (connectives)

    • OR (connectives)

  • Improved LIMIT query performance.

  • Improved performance of openCypher general aggregation queries.

Defects Fixed in This Engine Release

  • Fixed a Gremlin bug that allowed an edge to be connected to another edge.

  • Fixed a Gremlin bug that caused a sub-optimal join strategy to be chosen.

  • Fixed a Gremlin bug that caused serialization of nodes and relationships to stall when more than 100 properties were present.

  • Fixed a bug that slowed down query execution planning for queries with large graph patterns.

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

  • SPARQL version: 1.1

Upgrade Paths to Engine Release

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

You will not automatically upgrade 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.