Announcement Announcement Module
Collapse
No announcement yet.
Spring Data Graph 1.1.0.M1 with Neo4j support Released Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Spring Data Graph 1.1.0.M1 with Neo4j support Released

    Dear Spring Community,

    We are pleased to announce that a new milestone release (1.1.0.M1) of the Spring Data Graph project with Neo4j support is now available!

    The primary goal of the <b>Spring Data</B> project is to make it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud based data services.

    The Graph Neo4j module provides integration with the Neo4j graph database. Back in 2010, Rod Johnson and Emil Eifrem started brainstorming about Spring and Neo4j integration including transparent persistence and cross-store support. After an initial prototype it has been further developed in close cooperation between the VMware and Neo Technology development teams.

    To learn more about the project, visit the Spring Data Graph Project Homepage .

    The key changes in the Spring Data Graph 1.1.0.M1 milestone release include:
    • updated dependency to Neo4j 1.4.M04 including API updates to Neo4j 1.4 changes
    • updated dependency to AspectJ 1.6.12.M1 (also available with STS 2.7.0.M2)
    • fixed errors in the REST binding (multiple property setting, index operations)
    • added support for the Neo4j query language "Cypher" in entity annotations, introduced methods and repositories
    • added support for self-relationships
    • elementClass annotation attribute is now optional
    • updated documentation

    We are looking forward to your feedback on the forum or in the issue tracker.

    Project resources:
    Downloads | JavaDocs | Spring Data Graph Guide Book | Changelog

  • #2
    Are there any plans for Gremlin &amp; Spring Data Graph integration ?

    Hi to all,

    After a lot of recent research (Im quite new to Graphs), I 've come to consider Gremlin as one of the most awesome & powerful graph query (meta)languages - I think its the next standard.

    Along with groovy's dynamic nature, I envisage you can do very complex querying, inference & navigation - that's what the graph is all about! Playing through with the 1.1 release's matching features and grasping the direction & commitment evident by the tinkerpop team, I feel I want to look no further.

    Of course I love SDG too, so I was wondering if you have any plans for any kind of integration of Gremlin with SDG (repositories, querying etc)...

    The only slightly relevant discussion I can find is http://lists.neo4j.org/pipermail/use...ry/006955.html

    Best regards

    Comment


    • #3
      Could you please expand in more detail, which kind of integration you would like to see?

      Some areas a re overlapping, like frames, rexter and partly cypher and gremlin itself.

      That would also mean to pull in the groovy dependency. Which could be done in the "provided" scope.

      Thanks

      Michael

      Comment


      • #4
        Gremliin query support

        Michael thanks for your consideration.

        Well, I was referring to the Gremlin query metalanguage alone - not the whole tinkerpop stack.
        For instance Frames is contradictory to SDG. Ideally the blueprints lib could be used as an alternative graphdatasource, hence more Graph DBs could be plugged-in the SDG.

        But all that is NOT what I had in mind - having Neo4j, SpringDataGraph & Gremlin as my preferred toolkit.

        Reading your post http://groups.google.com/group/nosql...4060130f&pli=1
        I imagined (for Nodes & similarly for Repositories etc.) something like:

        @GraphGremlinQuery (“me.outE(‘works-at’).inV.inE(‘works-at’).outV”)
        Iterable<Person> colleagues;


        or simply

        @GraphGremlinQuery (“me.colleagues”)

        using https://github.com/tinkerpop/gremlin...-Defined-Steps.

        Of course those would have to be defined in another Groovy / Java class that is invoked at runtime, and that needs careful consideration. I do believe that the meta language and DSL features of Gremlin/Groovy are ideal for defining higher level queries in a high level framework.

        So, that is the kind “glueing” I had in mind and would care to see in SDG.

        Looking forwards to seeing your views.

        Thanks

        Agelos

        Comment

        Working...
        X