31–40 of 60 posts
What are the main reasons someone would use this over Neo4j? Is being open source the primary differentiator?
It handles far bigger dataset than Neo4J (even if performances are not great) and it is easier to use and maintain.
Earlier quoted context omitted.
have you used it on non-trivial scales? did it turn out ok for you? any major outstanding issues? asking because i've looked at it a couple of years back and decided to go with SQL but the project looked reeeaally interesting back then and it still might fit for new development.
I tried OrientDB. It's not clear how to use their fast data importer on data that's actually structured as a graph (instead of "hey, I've got a SQL database that I want to put into a graph database for some reason"). A couple of their employees have responded to me once but haven't actually answered the question. I also tried it before they had a fast data importer and... well, you need a fast data importer.
Have you already tried http://orientdb.com/docs/last/Graph-Batch-Insert.html?
In case you import data from a RDBMS, you can use Teleporter: http://orientdb.com/docs/last/Teleporter-Home.html.
Earlier quoted context omitted.
https://github.com/neo4j/neo4j
Neo4j, like all graph databases I've tried, is only okay with small data. Suppose I want to import a medium-sized graph into Neo4j. Medium-sized as in "fits on a hard disk and doesn't quite fit in RAM". One example would be importing DBPedia. Some people have come up with not-very-supported hacks for loading DBPedia into Neo4j. Some StackOverflow comments such as [1] will point you to them, and the GitHub pages will…
But after the import, it worked pretty well without issues and with decent performances. With decent meaning: not good for a Front End, good enough for running analysis in a back-end using a little bit of caching.
The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
there is also: https://github.com/dgraph-io/dgraph also a golang project as the title mentions, if this matters to anyone.
The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
Distributed (yes, really!) graph database, from a guy who was on Google's knowledge graph team.
The project has no activity in the last 6 months. I would like to see an open-source graph database that's being actively developed and maintained.
there is also: https://github.com/dgraph-io/dgraph also a golang project as the title mentions, if this matters to anyone.
Cayley seems uniquely suited for that, but its development activity is concerning. If anyone has any other suggestions, I'm all ears.
I've been looking at Cayley recently, for a project of ours. We want to ingest millions of Hearthstone replays (simple XML documents describing thousands of key/value deltas per game) and analyze the game state for every turn, etc. Cayley seems uniquely suited for that, but its development activity is concerning. If anyone has any other suggestions, I'm all ears.
https://github.com/dgraph-io/dgraph
Earlier quoted context omitted.
I tried OrientDB. It's not clear how to use their fast data importer on data that's actually structured as a graph (instead of "hey, I've got a SQL database that I want to put into a graph database for some reason"). A couple of their employees have responded to me once but haven't actually answered the question. I also tried it before they had a fast data importer and... well, you need a fast data importer.
What kind of data did you try to import into OrientDB? CSV? Or from any other GraphDB (GraphML format)? Have you already tried http://orientdb.com/docs/last/Graph-Batch-Insert.html ? In case you import data from a RDBMS, you can use Teleporter: http://orientdb.com/docs/last/Teleporter-Home.html .
Contrary to the assumptions of the OrientDB CSV tutorial, my edges are not being exported from a SQL database. The nodes aren't, for example, foreign keys into a SQL table. They don't have sequential IDs. They are just strings that identify the things that the edges connect. This is typical in N-Triples.
The triples are not currently in any kind of relational database, which I think is what Teleporter is about.
With the link to http://orientdb.com/docs/last/Graph-Batch-Insert.html, you seem to be asking me to write my own importer in Java. I'd rather not.