metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kasper Sørensen (JIRA) <j...@apache.org>
Subject [jira] [Created] (METAMODEL-234) Inconsistent column concept in Neo4j connector
Date Thu, 18 Feb 2016 12:52:18 GMT
Kasper Sørensen created METAMODEL-234:
-----------------------------------------

             Summary: Inconsistent column concept in Neo4j connector
                 Key: METAMODEL-234
                 URL: https://issues.apache.org/jira/browse/METAMODEL-234
             Project: Apache MetaModel
          Issue Type: Bug
    Affects Versions: 4.5.0
            Reporter: Kasper Sørensen


I'm giving the new Neo4j connector a spin and finding something quite strange. I'm using the
example Person/Movie database for my tests...

If I query only attributes of the node itself like this, then it works well:
{code}
SELECT name
FROM neo4j.Person a
WHERE name = 'Keanu Reeves'
{code}
(this returns one record)

But if I query also columns that represent relationships, then I get something that looks
like a product of many things. Query:
{code}
SELECT name, rel_ACTED_IN
FROM neo4j.Person a
WHERE name = 'Keanu Reeves'
{code}
(this returns 7 records)

I think I understand the wish to make the relationship links a part of the node's table, but
it doesn't comply with basic relational thinking in this case. When I add a single column
to my SELECT clause, then the row count should NOT change under any circumstances. It is like
it is doing an implicit join or so.

I suggest to instead provide the relationships as tables so they are valid and comparable
to the other table models that MetaModel expose.



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

Mime
View raw message