The latest patch for Neo4j Ops Manager is now available to download from the download centre and other usual repositories.
This is a patch release with a selection of bug fixes, and
- Support for Neo4j 5.17 and 4.4.30 versions in upgrade manager
- Support for dark mode to match the system preference
In the GraphQL team at Neo4j, we’ve been working on extending Aura to natively offer GraphQL Connectivity.
We’re now at the stage where people can start to try it and gives us some early feedback. If you’re interested in using GraphQL with Aura or just want to know more, then you can register your interest here
The Early Access will run between 1st April and 31st May and can be used with any Aura instance that is running in
GCP- other cloud platforms will be available later this year in a later Early Access.
All Aura V5 databases are now running the latest Neo4j version 5.17.
Neo4j GenAI Integrations
Compatibility with various generative AI services, including support for transforming text data into vector embeddings using VertexAI, OpenAI, or Amazon Bedrock. The resulting vector embeddings can be used together with Neo4j’s vector search indexes. Documentation is available here.
Language and Graph Model
- A string normalization function (NORMALIZE) and predicate expression (IS [NOT] NORMALIZED), making it possible to generate a canonical form of a Unicode string and determine if two Unicode strings are equivalent to each other. Documentation is available here and here.
- On attempting to create an index or constraint (CREATE INDEX|CONSTRAINT... IF NOT EXISTS), we now return a notification if the index/constraint to be created already exists. Similarly, on attempting to drop an index or constraint (DROP INDEX|CONSTRAINT... IF EXISTS), we now return a notification if the index/constraint to be dropped does not exist. Documentation is available here and here.
- Cache queries with obfuscated literals #24046 & Speed-up obfuscation #24019.
- Fix a bug where a query using a conjunction such as CREATE (:A&B) would create a node without labels.
- Fix a bug that would return a ‘WGS84 invalid coordinate error’ in a POINT INDEX distance calculation. This bug would occur for large search distances (> 11,936,226 m) where the search region perimeter crosses both poles (90,0 and -90,0).
- Fix issue with EXPLAIN and nested temporal types leading to a failed to pretty print RuntimeConstant error.
- Fix bugs in query obfuscation #23124.
Please refer to the changelog for full details of the changes.
Query log exports for AuraDB Professional instances will now only contain queries which complete in over 50ms.
This release of Data Importer brings a number of small changes that make using Data Importer that little bit easier :
Preview graph visualisation
The Import preview is now the last part of Workspace to migrate from the old visualisation to the new one used in Explore and Query. As well as being more visually consistent, it's now more responsive and easier to navigate.
We'll be exploring upping the limits on the number of preview nodes, do leave us feedback if you think that'd be useful.
- Files are now sorted alphabetically, making files easier to locate in longer lists.
- Files can now be globally expanded and collapsed making it easier to work with longer lists.
That's all for now. We're working on some big new capabilities in import, more on that to follow in the coming months 😀. As always keep your feedback coming on feedback.neo4j.com.
Team Members has been renamed to User Management.
To simplify terminology, we have renamed the existing Team Members function to
User Managementso it better reflects feature capability.
We're happy to announce that customizing your tenant name is now possible.
Simply go to the tenant selector in the top navigation, and hit the 'pencil' icon to change the name of your tenant.
We're pleased to announce the release of the 'Viewer' role for Aura user management.
For this release, we're focusing on empowering admin users with enhanced permissions control at both the Console and API levels. This feature allows admins to assign specific permissions based on roles, giving them the ability to prevent potentially destructive or costly actions within their tenant.
Viewers are able to:
- View tenant details
- View members of the tenant
- View and open all instances within a tenant
Please note, this role only applies to Aura Console access, and does not correspond or map to read-only access within the database.
User management and the viewer role will be released for self serve customers in Q1 2024.
Learn more about user management in our docs.
We are pleased to announce that Console Private Link Configuration is now generally available in AuraDB and AuraDS Enterprise across all three major 3 cloud platforms.
With Console Private Link Configuration, Aura Enterprise users with the
Adminrole can now self-configure private endpoints in the Aura Console. This gives authorised users access to advanced security tooling, which enables tighter control over the networks that the organisation's data traverses.
Console Private Link Configuration enables Aura Enterprise admins to configure a private connection between the Virtual Private Cloud (VPC) their applications are running in and the VPC where their Aura databases are hosted. This new capability enables Aura customers to use AWS PrivateLink, Azure Private Link and GCP Private Service Connect respectively, to configure the private connection. Once the connection has been established users can then have control over disabling (and re-enabling if required) public traffic, which will direct all traffic through the private endpoints and prevent it from traversing the public internet.
To get started simply head to the Aura console, navigate to the left hand panel and choose Network Access. Click the New Network Access Configuration button and follow the on-screen prompts to setup the connection. For more information please see the Aura Docs.
This is a maintenance release with the following small improvements and fixes:
- Now only non-composite database aliases are shown in the database dropdown
- Element-id now shown correctly in table view
- Added optional setting to specify read transactions on cypher queries