Amazon Neptune Engine Version 1.0.3.0.R2 (2020-10-12)
As of 2020-10-12, engine version 1.0.3.0.R2 is being generally deployed. Please note that it takes several days for a new release to become available in every region.
Improvements in This Engine Release
Improved performance for the Gremlin
properties()
step.Added details about
BindOp
andMultiplexerOp
in explain and profile reports.For SPARQL query responses, added
charset
to the Content-Type header, enabling HTTP clients to recognize the charset being used automatically.
Defects Fixed in This Engine Release
Fixed a SPARQL bug where
CancellationException
was not handled.Fixed a SPARQL bug where queries containing nested optionals did not work correctly.
Fixed a SPARQL bug in LOAD where a
ConcurrentModificationException
could cause a query to hang.Fixed a SPARQL bug that prevented query responses from being gzip-compressed.
Fixed a Gremlin bug in the
groupBy()
step.Fixed a Gremlin bug related to the use of an
aggregate()
step inside alocal()
step.Fixed a Gremlin bug related to using
bothE()
followed by a predicate that uses aggregate values.Fixed a Gremlin bug related to using the
bothE()
step with therepeat()
step.Fixed a potential Gremlin memory leak related to the
both()
step.Fixed a bug where request metrics were missing because an endpoint ending in '/' was not being handled correctly.
Fixed a bug that could raise a
ThrottlingException
even when the request queue is not full.Fixed a bug in fetching load status when a load fails for a reason such as
LOAD_DATA_FAILED_DUE_TO_FEED_MODIFIED_OR_DELETE
.
Query-Language Versions Supported in This Release
Before upgrading a DB cluster to version 1.0.3.0.R2, 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 1.0.3.0.R2
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 1.0.3.0.R2 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.3.0 \ --apply-immediately
For Windows:
aws neptune modify-db-cluster ^ --db-cluster-identifier
(your-neptune-cluster)
^ --engine-version 1.0.3.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.
Always test before you upgrade
When a new major or minor Neptune engine version is released, always test your Neptune applications on it first before upgrading to it. Even a minor upgrade could introduce new features or behavior that would affect your code.
Start by comparing the release notes pages from your current version to those of the targeted version to see if there will be changes in query language versions or other breaking changes.
The best way to test a new version before upgrading your production DB cluster is to clone your production cluster so that the clone is running the new engine version. You can then run queries on the clone without affecting the production DB cluster.
Always create a manual snapshot before you upgrade
Before performing an upgrade, we strongly recommend that you always create a manual snapshot of your DB cluster. Having an automatic snapshot only offers short-term protection, whereas a manual snapshot remains available until you explicitly delete it.
In certain cases Neptune creates a manual snapshot for you as a part of the upgrade process, but you should not rely on this, and should create your own manual snapshot in any case.
When you are certain that you won't need to revert your DB cluster to its
pre-upgrade state, you can explicitly delete the manual snapshot that you created
yourself, as well as the manual snapshot that Neptune might have created. If Neptune
creates a manual snapshot, it will have a name that begins with preupgrade
,
followed by the name of your DB cluster, the source engine version, the target engine
version, and the date.
Note
If you are trying to upgrade while a pending action is in process, you may encounter an error such as the following:
We're sorry, your request to modify DB cluster (cluster identifier) has failed. Cannot modify engine version because instance (instance identifier) is running on an old configuration. Apply any pending maintenance actions on the instance before proceeding with the upgrade.
If you encounter this error, wait for the pending action to finish, or trigger a maintenance window immediately to let the previous upgrade complete.
For more information about upgrading your engine version, see Maintaining your Amazon Neptune DB Cluster. If you have any questions or concerns, the Amazon Support
team is available on the community forums and through Amazon Premium Support