You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2017/11/04 20:32:00 UTC
[jira] [Closed] (TINKERPOP-1826) Source and Target reversed in
GraphMLReader?
[ https://issues.apache.org/jira/browse/TINKERPOP-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez closed TINKERPOP-1826.
-----------------------------------------
Resolution: Not A Problem
That is correct.
out -> source
in -> target
out---label-->in
> Source and Target reversed in GraphMLReader?
> --------------------------------------------
>
> Key: TINKERPOP-1826
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1826
> Project: TinkerPop
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: John Lockwood
> Assignee: Marko A. Rodriguez
> Priority: Critical
>
> Hi,
> In GraphMLReader.java (circa lines 121-122), find the following lines:
> final String vertexIdOut = reader.getAttributeValue(null, GraphMLTokens.SOURCE);
> final String vertexIdIn = reader.getAttributeValue(null, GraphMLTokens.TARGET);
> On the face of it this looks backwards. Also, looking at the data I'm trying to parse, it does look like the graphML is correctly going from source -> target in the graphml file, not the other way around as suggested here.
> Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)