My knowledge of graph databases is pretty sparse I must admit. I do recall another request for something similar, namely semantic web models [1] but we didn't get that far in designing how it would work...
I guess my primary stand would be that "as long as we can map it to a tabular format of some sort, then it is good". MetaModel has a schema/table/column like model and that allows us to make our metadata and query API quite consistent ... Of course I might be missing some good alternative way of modelling stuff. For the graph databases, maybe each node could be modelled as a table, and each relation as another? Just a idea with no real experience to draw on :-) [1] http://mail-archives.apache.org/mod_mbox/metamodel-dev/201402.mbox/%3CCAFnmbpU80MR4J+BT7VnCQSpKYPBtgMDChKm=rl2njzcrfo2...@mail.gmail.com%3E 2014-07-08 11:19 GMT+02:00 Ankit Kumar <[email protected]>: > Hi All, > > I wanted to discuss a new feature addition to Metamodel. > > Feature addition: - Add support to work with graph databases in Metamodel. > > Reason: - As metamodel is the storage abstraction layer above most of the > well know datastores, graph databases are getting used more and more. Isn't > it time to add that support if possible? > > Challenges: - Graph databases are quite different in the way they store, > the API and the query language used is quite different so it might not be > straightforward to add this. > I specifically checked the Neo4J database and it does have a Java API for > querying, it also has Spring Data project(do not know if we can use that or > use some aspect from it). > > If someone has used a graph database through Java and also is using > Metamodel may be can provide some valuable insights. > > Do please share your thoughts on the same. > > Regards > Ankit >
