Neo4j Ops Manager 1.8 is a maintenance release, and is now available to download for Enterprise Edition self-managed customers from the download page.

This release of Data Importer brings two new features:

We've made a slight tweak to the Preview feature, allowing you to optionally preview selected parts of your our graph. If you have a particularly complex model, it can sometimes be hard to see how all the different nodes and relationship types being previewed are linking. In these scenarios you can use "Preview selected" to only preview selected parts of the model. This can help you validate specific parts of the model are mapped as expected. In the example below, only the Product, Supplier and SUPPLIES parts of the model will be previewed when using the "Preview selected" option.

The Data Importer UI gives you a convenient way to generate your graph model and map data, but what happens if you want to take the import logic and use it somewhere else without the UI? Or what if the Data Importer UI doesn't quite allow the complex transformations that you need?

For these scenarios, we are now providing you the option to view and download a Cypher script representing your model and mapping. You can use these as-is, or adapt for more complex needs.

Examples of where you might use this generated code include:

The load script itself is commented to help you understand the purpose of the different parts and where you might need to make changes, depending on where you're running it.

You can also choose to download the files with your script, which will give you a handy zip of the script and your files.

We hope you enjoy using these new features and as always please head over to https://feedback.neo4j.com/data-importer with any feedback.

This is a minor maintenance release with the following fixes and improvements:

Aura API provides Neo4j Aura Enterprise customers with a programmatic way to perform database operations in Neo4j Aura.

The ability to programmatically provision and manage databases is something that Aura Enterprise customers have been asking us for so that they can easily integrate Aura into their end-to-end pipelines, and automate the day-to-day management and running of their Aura estate.

Since Summer 2022, we’ve been on a journey to provide this ability to our customers. After a successful Beta program, we’re pleased to move to v1 (General Availability) of Aura API for our Enterprise customers.

Now with Aura API, all Enterprise customers have a secure programmatic way to Create, List, Pause/Resume, Resize, Backup, Restore, Clone, and Delete Neo4j databases as their business requires. Aura API is REST based making it easy to call from scripts or integrate with operational applications so that Aura databases can be managed without the need for any manual actions in the Console.

Please see our API docs for more information on how to get started, and reach out to your Account Manager or the Aura Support Team if you have any questions.

Happy Graphing

Aura Product Team

Patch 1.7.3 for Neo4j Ops Manager is now available to download.

Prototype with / Create a GraphQL API with your Aura instance in a few seconds with the GraphQL Toolbox

For further information please see our docs.

Please give it a try and share your feedback!

Thanks

The GraphQL Product Team

Neo4j Bloom Enterprise offers additional features including storage of multiple Scenes, and sharing Scenes & Perspectives with other users based on database role.

We are now expanding our Early Access program, which offers Bloom Enterprise to interested organizations at no additional charge for one year.

For more information, please get in touch with your Customer Success Manager, or raise a support ticket to express your interest!

Thanks

The Aura & Bloom Product Teams

We are excited to announce that we have released V1Beta4 of our API. This new version brings some significant improvements and enhancements to our service and we want to ensure you are aware of the changes.

Please read the following carefully as there are a number of changes encompassing new endpoints, modifications to existing ones and a few breaking changes with V1Beta4

This is new functionality that we’re bringing to V1Beta4. It’s not expected that these will cause issues and can be introduced at your convenience. We do , as always, recommend testing.

We have introduced this new endpoint to retrieve details of a specific snapshot associated with an instance.

It is now possible to choose which snapshot of the source instance that will be used when overwriting an existing instance. To do this, include in the request body with when performing a request.

We consider these changes to be those that you can adapt to at your discretion and timeline without disruption to existing functionality. Nevertheless, we recommend that you test your application to confirm your integration is working as expected.

Creating instances requires ‘cloud_provider’ to be supplied with

When making creating an instance the cloud provider must be specified as part of the request body. For example, to use GCP , add to the request body.

Additional fields and are returned as part of the response.

Full instance details are returned in the request response when using the following endpoints and operations:

When creating a snapshot, this endpoint now returns in the request response.

This endpoint now includes cloud provider information as part of the information in each instance.

A breaking change is a change that may require you to make changes to your application in order to avoid disruption to your integration with the Aura API. The following are changes we consider breaking.

All POST/PATCH requests require the header to be specified with the value for example:

When using GET /tenants the field has been relocated to each entry in the list.

We understand that these changes may require some modifications to your existing integration. To ensure a smooth transition to V1Beta4, we recommend reviewing your codebase and updating it accordingly to accommodate these changes. For more information please see Aura API Docs or go direct to our latest V1Beta4 swagger spec.

If you have any questions or need assistance with the migration, please don’t hesitate to reach out to our support team. We are here to help you throughout the process.

Thanks

The Aura Product Team

This is a minor maintenance update with a number of small fixes.

Patch 1.7.2 for Neo4j Ops Manager is now available to download.

This contains a small number of fixes which were not ready in time for the 1.7 release:

We recommend that you apply this patch version to your implementation.