Amazon Neptune Engine Version (2020-08-03) - 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-08-03)

As of 2020-08-03, 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

Improvements in This Engine Release

  • You can now provide the size of batch requests to ElasticSearch for full- text searches in Gremlin.

  • Improved memory usage for SPARQL GROUP BY queries.

  • Added a new Gremlin query optimizer to prune certain unbound filters.

  • Increased the maximum time a WebSocket connection authenticated using IAM can stay open, from 36 hours to 10 days.

Defects Fixed in This Engine Release

  • Fixed a bug where if you sent an un-encoded URL parameter in a POST request, Neptune returned an HTTP status code of 500 and an InternalServerErrorException. Now Neptune returns an HTTP status code of 400 and a BadRequestException, with the message: Failure to process the POST request parameters.

  • Fixed a Gremlin bug where a WebSocket connection failure was not correctly reported.

  • Fixed a Gremlin bug involving disappearing sideEffects.

  • Fixed a Gremlin bug where the full-text search batchsize parameter was not properly supported.

  • Fixed a Gremlin bug to handle toV and fromV individually for each direction on bothE.

  • Fixed a Gremlin bug involving Edge pathType in the hasLabel step.

  • Fixed a SPARQL bug where join re-ordering with static bindings was not working correctly.

  • Fixed a SPARQL UPDATE LOAD bug where an unavailable Amazon S3 bucket was not correctly reported.

  • Fixed a SPARQL bug where an issue with a SERVICE node in a subquery was not correctly reported.

  • Fixed a SPARQL bug in which queries containing nested FILTER EXISTS or FILTER NOT EXISTS conditions were not being properly evaluated.

  • Fixed a SPARQL bug to correctly handle duplicate generated bindings when calling SPARQL Service endpoints through generate queries.

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

  • SPARQL version: 1.1

Upgrade Paths to Engine Release

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

If your cluster has its AutoMinorVersionUpgrade parameter set to True, your cluster will be upgraded to this engine release automatically two to three weeks after the date of this release, during a maintenance window.

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.