No description provided.
Created datomic graph module
Update of parent pom
Updated datomic dependencies
Thanks for your contribution. I just gave a quick glance to review this pull request from a Blueprints API implementation consistency perspective. One thing I noticed here:
The Element setProperty method should throw an IllegalArgumentException if the value is not a valid type expected by the underlying graph. If I'm following the diff right, the IllegalArgumentException is thrown by way of a call from here:
Is that correct?
That is correct. Just tested it out to make sure:
Vertex davy = graph.addVertex(null);
Exception in thread "main" java.lang.IllegalArgumentException: Object type com.tinkerpop.blueprints.pgm.impls.datomic.Test not supported
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Updated implementation to support IndexableGraph interface
Updated implementation to allows for the creation of automatic indexe…
…s (basically filtering on attribute keys)
- Updated to version 0.1.3007 of Datomic
- Making use of the raw index access where appropriate
Adde datomic logo for docs
Updated to latest datomic build (0.1.3065)
I would love to see this get merged in
First update to support the 2.1.0 Blueprints API
Merge remote-tracking branch 'upstream/master'
Improved overall iteration
DatomicGraph is now implementing new KeyIndexableGraph interface
I think we should consider options for getting Datomic into mainline after we release 2.1 in the coming weeks. Please let me know if you think there is anything we need to think about or consider in terms of doing that.
Not a lot I guess. The only disadvantage I can think off is that people need to manually install the datomic dependency.
Time-aware extensions to the core blueprints API
Updated datomic-graph implementation with time-aware features (includ…
…ing time-scoped iteration)
Added datomic(-free) dependency to the project deps ... (is now autom…
…atically uploaded to clojars at build time)
An example demonstrating the use of time-scoped iteration of vertices…
… and edges
after a number of discussions on tinkerpop-contributors, it appears we've basically decided to keep your blueprints implementation separate from the mainline of blueprints development. is it ok to close this pull request?
from there it would be cool to collaborate with you to build rexster configuration classes in your repos. i think i could do that pretty quickly for you if you can talk to me a little bit about what the configuration options are.
Ok. Will close this pull request and create a new repository specifically for FluxGraph.
will FluxGraph cover both the mongodb and dataomic implementations?