Hello, it hasn’t been long since our last release post, but we’re happy to announce that Memgraph 1.6 is ready to be used and tested out!

A new version of Memgraph isn’t the only thing we’re proud of. With it comes our refreshed and improved documentation page. There, you should find answers to any questions you have about Memgraph, including the features from this release!

We set sails in a new direction, right into the streaming world. But getting there is not easy, so a lot of work is still ahead of us.

In the last release, we introduced triggers. In short, when something changes in the data Memgraph has stored, a certain query can be executed. Now, we need to allow you to continuously and easily update your graphs!

Connect to Kafka

For sure, the biggest name in the streaming world is Kafka. With the newest Memgraph, you can connect to a Kafka cluster and run any kind of openCypher queries based on the Kafka messages Memgraph receives. Using similar techniques as for defining the Query Modules, you can easily define a transformation procedure that will be called for each Kafka message. The same rules apply as for the Query Modules, you can do anything (as long as you return a query in the end…). Creating a streaming connection isn’t the only thing you can do. You can stop it, start it, drop it, and of course, check if it works as intended. Just tell Memgraph how to connect to your existing Kafka cluster and let it do the rest!

If you’re wondering how it all looks in practice, check out our nice example.

New Isolation Levels

For some time, the word isolation isn’t something you like to see a lot. Nevertheless, we had to expand our isolation levels. Until now, SNAPSHOT ISOLATION was your only option, but now you can use READ COMMITTED and READ UNCOMMITTED. Some of the isolation levels are hard to explain, but I think it’s not the case here. You can set a default level using a config or through a query. When using a query multiple possibilities show up. You can set the isolation level for every transaction, for the current session, or just for the next transaction.

I didn’t give you too many details, but you can find everything explained here.

There’s still more

If connecting to Kafka and using a different isolation level is still not enough, here’s a rundown of some other things we introduced with this version:

• disabling the LOAD CSV clause using a configuration flag
• generating a snapshot with a query
• fixed random query timeouts on machines with AMD Ryzen 7 and M1 chips
• introduced global allocators for our Query Modules C-API

For more details, check out our Change Log.

So go and try it out! You can download the 1.6 version here. If you catch any bugs or generally weird behavior, please drop us a line on our forum. And remember, if you need any kind of information about Memgraph, the documentation site will always be by your side.

Happy hacking!