By Andreas Kollegger, Senior Product Designer | April 15, 2016
Neo4j 3.0 is coming soon, and we would like to ask you today for your feedback on our first release candidate.
For your review
Neo4j 3.0-RC1 previews some significant new features which we’d love for you to review.
- Java stored procedures:
CALLthem on their own or mix them within a more complex Cypher statement using
CALL ... YIELD.
- Neo4j Sync: A companion cloud service for the Neo4j Browser that stores scripts, graph style sheets and history.
- Operability changes: Important changes to the directory layout and the configuration of Neo4j.
- Documentation library: Introducing a collection of focused publications, starting with a Developer Manual and Operations Manual.
We’ve already discovered some issues that you should know about. Notably, you may encounter these:
- Neo4j Browser only works with authenticated Bolt connections. You must either enable authentication on the server or disable Bolt in Neo4j Browser settings.
If you really love what we built you can tell the world on Twitter; if not, tell us directly. For every tweet tagged #neo4j #feedback that provides a lovely quote and a picture we raffle one rare blue Neo4j water bottle per day for each of the next 12 days.
All the Links You Need
Download Neo4j 3.0.0-RC1, grab a driver for your language, then peruse the new documentation.
The Neo4j Team
About the Author
Andreas Kollegger, Senior Product Designer
Andreas Kollegger is a technological humanist. Starting at NASA, Andreas designed systems from scratch to support science missions. Then in Zambia, he built medical informatics systems that complement technology with social good. Now with Neo4j, he is democratizing graph databases which elevate understanding by emphasizing relationships.
Andreas joined Neo4j as an early member of core engineering. He has now taken on the role of Senior Product Designer, crafting a developer experience that balances simplicity with power.
From the CEO
Have a Graph Question?
Reach out and connect with the Neo4j staff.Stackoverflow
Share your Graph Story?
Email us: email@example.com