Amazon Neptune Engine Version 1.0.2.0 (2019-11-08)
IMPORTANT: THIS ENGINE VERSION IS NOW DEPRECATED
Starting from 2020-05-19, no new instances using this engine version will be created.
This engine version is now superseded by version 1.0.2.1, which contains all the bug fixes in this version as well as additional features such as full-text search integration, OSGP index support, and database snapshot cluster copy across Amazon Regions.
Starting June 1, 2020, Neptune will automatically upgrade any cluster running this engine version to the latest patch of version 1.0.2.1 during the next maintenance window. You can upgrade manually before then, as described here.
If you have any issues with the upgrade, please contact us through Amazon Support
Subsequent Patch Releases for This Release
New Features in This Engine Release
In addition to maintenance updates, this release adds new functionality to support more than one engine version at a time (see Neptune engine updates).
As a result, the numbering of engine releases has changed (see Neptune Engine version numbering).
Query-Language Versions Supported in This Release
Before upgrading a DB cluster to version 1.0.2.0, 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.0
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 1.0.2.0 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.0 \ --apply-immediately
For Windows:
aws neptune modify-db-cluster ^ --db-cluster-identifier
(your-neptune-cluster)
^ --engine-version 1.0.2.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