You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by "Tomasz Guzialek (JIRA)" <ji...@apache.org> on 2014/11/26 10:41:13 UTC

[jira] [Commented] (METAMODEL-99) Neo4j connector.

    [ https://issues.apache.org/jira/browse/METAMODEL-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225957#comment-14225957 ] 

Tomasz Guzialek commented on METAMODEL-99:
------------------------------------------

Neo4j-jdbc accepts a query as a string in Cypher, not in SQL string as many might expect. Therefore, it is not that useful as I hoped. I decided to use REST API directly after all. REST API needs to be used anyways as getting all the properties per node is currently not available in Cypher, but possible through REST.

The coode lies in my fork: https://github.com/tomaszguzialek/incubator-metamodel/tree/METAMODEL-99 Included basic attempt to infer the schema and materialize it - tested with very limited scope of queries. Tests pass locally, but fail on Travis - probably because of different Neo4j version.

The code demands major refactorizations - applied "surround with try/catch and don't bother me now" approach.

> Neo4j connector.
> ----------------
>
>                 Key: METAMODEL-99
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-99
>             Project: MetaModel
>          Issue Type: Improvement
>            Reporter: Tomasz Guzialek
>            Assignee: Tomasz Guzialek
>
> A new connector for Neo4j graph database. 
> Approach: map each Neo4j graph label to a MetaModel table. Trying to use JDBC connector for Neo4j (http://www.neo4j.org/develop/tools/jdbc)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)