Changelog

Follow up on the latest improvements and updates.

RSS

This maintenance release includes important security updates.
3rd party Graph Apps are now restricted. Installation of applications via the Gallery App, file protocol or deep linking will no longer work.
Neo4j Labs Graph Apps are now pre-installed.
Bundled Bloom version 2.11.0
We are pleased to announce the general availability of
Customer Metric Integration
for Aura Enterprise customers. It is accessed from the Operations section of the sidebar using the Metric Integration item.
CMI Endpoints
Customer Metric Integration takes the content of Aura Advanced Metrics and allows you to integrate this data into your observability platform of choice using a secured Prometheus endpoint. Once the data is integrated in your own system, this can be used to generate alerts and notifications, if desired, over the managed Aura instance(s). The endpoints provided are per instance, or for the whole tenant.
An overview of the setup tasks is as follows:-
CMI Setup
Once a user has been set up with the metric integration role and has a valid API key, your observability platform of choice can be securely configured to access the endpoint(s) and collect the metrics data on a periodic basis.
The recommended collection interval for metrics is in the range of 30 seconds up to 2 minutes, depending on requirements. The metrics endpoint caches metrics for 30 seconds and polling more frequently than this will not retrieve different data.
Full setup and reference documentation is provided from the console page.
Next steps and charges
Aura Database and Analytics services are business critical for our users. We have requests to introduce more capabilities enabling access to logs and metrics to derive actionable insights using your choice of monitoring platform.
We have a strong roadmap of observability sharing features including metrics, security logs, query logs and other capabilities. Many of the associated logs can be of significant size hence we will introduce in the future a new consumption based billing model including cloud egress costs.
We believe observability is of paramount importance hence we have decided to make
Customer Metric Integration
available for you initially at no extra charge.
Aura and Ops Manager product teams.

new

improved

AuraDB Enterprise

AuraDB Professional

AuraDB Free

AuraDS Self-Start

AuraDS Enterprise

Neo4j Aura Database feature update!

The following core Neo4j Database features are now available for users in Aura:
  • Anonymous usage data reporting: Neo4j sends a small amount of anonymous usage data back to Neo4j. This helps us understand how our products are used and improve them. The reporting can be disabled with the configuration setting dbms.usage_report.enabled=false. For a full description of the reported data, please refer to the Anonymous usage data report documentation page.
  • Add a new deprecatedBy column to SHOW PROCEDURES and SHOW FUNCTION to show if a procedure/function has a replacement when it has been deprecated.
  • It is now possible to
    reference variables from within a Quantified Path Pattern (QPP) that are not defined directly inside
    the QPP. For example:
MATCH (x)
MATCH ((a)--(b) WHERE a.h >x.h)*(s)-->(u)
RETURN *
To use x as a predicate, it is no longer necessary for it to have been previously defined; so this query can now be rewritten as:
MATCH (x)-->(y)((a)-[e]->(b) WHERE a.h > x.h)*
RETURN *
  • To further comply with the GQL specification, we have extended the existing trim(), ltrim() and rtrim() functions to optionally allow the specification of which characters to trim, as well as the addition of a btrim() function which trims both ends of a string. For example, RETURN BTRIM('xyzzyNeo4jzyx', 'xyz') returns ‘Neo4j’. For details, please refer to the String function - Cypher manual.
  • Deprecate property references that depend on the order of evaluation
    within a MERGE clause, for example:
MERGE (a {prop:'p'})-[:T]->(b {prop:a.prop}).
The following is still allowed:
MATCH (a {prop:'p'})
MERGE (b {prop:a.prop}).
  • Existing trim(), ltrim() and rtrim() functions optionally allow the specification of which characters to trim, whilst a new btrim() function which trims both ends of a string.
  • It is now possible to reference elements from within a Quantified Path Pattern that are not directly adjacent to the QPP.
We hope you enjoy these new capabilities, please refer to the Neo4j changelog for full details of the changes.

new

AuraDB Enterprise

AuraDB Professional

Query API - Early Access Program

The Query API allows the execution of Cypher statements against a Neo4j server through HTTP requests. This capability was released with Neo4j. 5.19 and is on the way to being available in Aura. An important waypoint on that journey is the Early Access Program where we open the Query API to a limited audience for feedback and external validation. Information on the Query API is available in the documentation here:- Query API
If you'd like to take part in the Early Access Program for the Query API on Aura, then please complete this form - Query API EAP Sign Up
You will be asked for the Aura instance's connection URI that you intend to use with the Query API. To find this, log into the Aura Console and select the desired Aura instance. The Connection URI is shown at the top of the screen as highlighted in red in the example screenshot below.
ConnectionURI
If you want to find out more about taking part, please get in touch with myself or Greg
Regards
Jonathan Giffard, PM , jon.giffard@neo4j.com
Greg Woods, Eng, gregory.woods@neo4j.com

new

AuraDB Enterprise

AuraDB Professional

AuraDB Free

Data Importer

New in Data Importer - Node property indexes

The latest release of Data Importer brings support for node property indexes. For properties you refer to frequently, indexes can speed up your queries dramatically. It's now possible to configure indexes directly in data importer. You'll find the UI to configure indexes in the details panel:
constraints-tab
Read the docs to learn more!
We are pleased to announce the general availability of Customer Managed Keys for Aura Enterprise customers on AWS. You can now protect your data in Aura using your own managed keys created using AWS Key Management Service (KMS).
To start using Customer Managed Keys, head to the Aura Console and choose Customer Managed Key in the left hand navigation. You can then create a new Customer Managed Key here. Remember to copy the Key ARN from AWS and match the AWS region where the key is located.
Create New Customer Managed Key 2
Once the Customer Managed Key have been created and validated with AWS, you can start using it to encrypt a new v5 instance. Head back to Instances of the selected product (AuraDB or AuraDS) and click New Instance. You can then choose to use your Customer Managed Key under Encryption Settings.
Create New Instance
To learn more about Customer Managed Keys, head over to the Aura documentation. Happy graphing!

new

AuraDB Enterprise

AuraDB Professional

AuraDB Free

AuraDS Self-Start

AuraDS Enterprise

Latest Neo4j version 5.19 on Aura!

All Aura v5 databases are now running the latest Neo4j version 5.19.
Highlights include:
Surface for Developers and Data Scientists
GenAI plugin:
  • Support for Vertex AI taskType and title embedding parameters
  • Support for Vertex AI vector encoding models textembedding-gecko@002, textembedding-gecko@003, and textembedding-gecko-multilingual@001.
Language and Graph Model
  • An optional keyword DISTINCT can now be used after UNION as the explicit form of a UNION with duplicate removal. Users now have the options of UNION ALL, UNION DISTINCT or UNION (the existing behavior, which behaves as UNION DISTINCT). Documentation is available here.
  • For LIST and STRING concatenation, || can now be used as a synonym of + Documentation is available here and here.
Scale and Availability
  • A new and improved eagerness analysis algorithm reduces the number of eager operators and improves explainability and performance, and reduces memory utilization.
Operability & Observability
  • Plan descriptions produced by EXPLAIN and PROFILE now provide additional information about planned eager operators in the 'Detail' column, improving explainability.
Platform & Supportability
  • In line with OpenID Connect Core 1.0 updates to errata set 2, remove checks on the azp claim in OIDC tokens when there are multiple values in the aud claim.
  • Update Apache Shiro to 2.0.0
Security
  • Set permissions on /var/lib/neo4j/bin to 755
Fixes
Kernel Fixes
  • A fix that avoids database issues following a leader switch in clustered setups on 5.18. We now perform an extra lease check to ensure a token's replicated state is current before checking its existence in the database. This prevents attempts to create duplicate tokens post-switch, which can cause database panics.
  • Fixed transaction logs metrics that weren't incremented in a cluster setup.
  • Fixes a rare issue in clustered setups where frequent leader switches could cause some internal record IDs to be reused.
  • Fixes a problem when the verbose flag was set while using neo4j-admin to output a dump file. This would cause both outputs to be written to standard out, resulting in garbage. When running neo4j-admin database dump --to-stdout neo4j any logging output is now directed to standard err, and the database dump will be directed to standard out.
Cypher Fixes
  • Bug fixes and security updates on IMMUTABLE privileges
  • Fix bug in pipelined runtime where a fused pipeline following a CALL IN TRANSACTION subquery without RETURN could have generated incorrect code for reading from input rows, which could lead to an IndexOutOfBoundsException.
Please refer to the changelog for full details of the changes.

new

AuraDB Professional

AuraDS Self-Start

Advanced Metrics now available for Aura Professional!

We are pleased to announce the general availability of Advanced Metrics for Aura Professional customers in the Aura console. It is accessed from the current metrics tab of an instance card in the Aura console, by clicking on the Advanced Metrics button next to the time range selector, and will open in a new tab.
AAM1
Advanced Metrics offers an expanded set of metrics divided into three categories:
  • Resources
    - Information about the resource utilization of your database instances and their underlying hardware.
  • Instance
    - In-depth information about how your Neo4j instance is running.
  • Database
    - This section contains information specific to your Aura database.
Interactive charts
Advanced Metrics features interactive charts that let you adjust the view to your needs.
  • Zoom
    - All charts can be zoomed in by selecting and dragging. The zoom level applies to all charts on the page, letting you easily surface correlated events across multiple metrics. Reset the view using the context menu or double-clicking anywhere within the chart.
  • Relative or absolute values
    - Certain charts can be toggled to show either relative or absolute values.
  • Enable and disable lines
    - In charts containing more than one data series, lines can be toggled simply by clicking in the chart legend.
NOTE: Professional users will see only a single data series on the charts. Multiple series is an Enterprise feature
interactive
Expanded view
Use the Expand option in the context menu of any chart to maximize the chart on the screen. All chart interactions are still available in expanded mode. If you adjust the zoom level in an expanded chart the zoom level is seamlessly applied to all charts in the background.
expand
Next steps
Happy charting!
Aura and Ops Manager product teams.

new

AuraDB Enterprise

AuraDS Enterprise

Advanced Metrics now available for Aura Enterprise!

We are pleased to announce the general availability of Advanced Metrics for Aura Enterprise customers in the Aura console. It is accessed from the current metrics tab of an instance card in the Aura console, by clicking on the Advanced Metrics button next to the time range selector, and will open in a new tab.
AAM1
Advanced Metrics offers an expanded set of metrics divided into three categories:
  • Resources
    - Information about the resource utilization of your database instances and their underlying hardware.
  • Instance
    - In-depth information about how your Neo4j instance is running.
  • Database
    - This section contains information specific to your Aura database.
Aggregations
As Aura Enterprise instances run with high availability, the charts in Advanced Metrics can provide some aggregate views of the servers providing the high availability. For example, CPU usage can show the maximum, average (mean) and minimum usage of the servers supporting the database.
Interactive charts
Advanced Metrics features interactive charts that let you adjust the view to your needs.
  • Zoom
    - All charts can be zoomed in by selecting and dragging. The zoom level applies to all charts on the page, letting you easily surface correlated events across multiple metrics. Reset the view using the context menu or double-clicking anywhere within the chart.
  • Relative or absolute values
    - Certain charts can be toggled to show either relative or absolute values.
  • Enable and disable lines
    - In charts containing more than one data series, lines can be toggled simply by clicking in the chart legend.
interactive
Expanded view
Use the Expand option in the context menu of any chart to maximize the chart on the screen. All chart interactions are still available in expanded mode. If you adjust the zoom level in an expanded chart the zoom level is seamlessly applied to all charts in the background.
expand
Next steps
Advanced Metrics are being made available for Aura Enterprise instances initially. It will also be made available to Aura Professional instances soon.
Happy charting!
Aura and Ops Manager product teams.

new

AuraDB Enterprise

AuraDB Professional

AuraDB Free

AuraDS Self-Start

AuraDS Enterprise

Latest Neo4j version 5.18 on Aura!

All Aura v5 databases are now running the latest Neo4j version 5.18.
Highlights
Surface for Developers and Data Scientists
  • The GenAI Plugin introduces and defaults to a new vector search index provider, vector-2.0, which brings: Support for up to 4096 dimensional vectors and integral element vectors, An improved cosine similarity implementation & Relationship vector indexes.
  • Added support in the GenAI Plugin for the OpenAI text-embedding-3-large and text-embedding-3-small models. These new models have the optional dimensions::INTEGER configuration option, as they support shortening on both OpenAI and Azure OpenAI.
  • Added support for using Azure OpenAI as the embedding provider in the GenAI Plugin. (Documentation of the GenAI Plugin is here.)
Language and Graph Model
  • Extended the Simple CASE expression to allow predicate expressions (e.g. WHEN IS NOT NULL THEN 1) and comparison operators (e.g. WHEN <1 THEN 'small', and also to allow comma-separated WHEN operands (e.g. WHEN 'red', 'blue', 'green' THEN 'colourful'). (Documentation is here.)
  • INSERT can now be used as a synonym of CREATE when creating graph elements (documentation is available here).
Vector index updates:
  • Added pairwise vector similarity functions vector.similarity.euclidean and vector.similarity.cosine (documentation is available here).
  • CREATE VECTOR INDEX for relationship vector indexes (requires 'vector-2.0' index provider)
  • Support for indexes and queries with LIST<INTEGER|FLOAT> to help accommodate some implicit conversions that can occur with Cypher.
  • Documentation for vector indexes is here; see also documentation for syntax and procedures.
Please refer to the changelog for full details of the changes.
Load More