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

ASF GitHub Bot commented on TINKERPOP-2006:
-------------------------------------------

Github user svanteschubert commented on the issue:

    https://github.com/apache/tinkerpop/pull/891
  
    What is the correct GitHub / Tinkerpop procedure to update a patch? Do you 
have a pointer?
    
    I decided to start from scratch and cloned a fresh Tinkerpop repro, to 
start a fresh git branch from the latest sources. 
    
    But the master has build problems on my machine with the latest patches on 
Windows (JDK 181).
    Do you build as well on Windows? Going to reboot here.. ;-)
    



> GraphML serialization invalid if a vertex and edge have similar named property
> ------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2006
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2006
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 3.3.3
>            Reporter: Svante Schubert
>            Priority: Trivial
>
> I have created a graph using the Tinkerpop Graph and required for Gephi 
> visualization a property called color on edges and vertices to be coloured.
> The current gremlin-core serialization creates the following two key elements 
> in GraphML
> <key id="color" for="node" attr.name="color" attr.type="string"></key>
> <key id="color" for="edge" attr.name="color" attr.type="string"></key>
> the id attribute is an internal name, but have to be different.
> I would suggest a patch to check for an intersection of the edge & vertices 
> keys and add for those keys an additional differentiating letter like:
> <key id="colorV" for="node" attr.name="color" attr.type="string"></key>
> <key id="colorE" for="edge" attr.name="color" attr.type="string"></key>
>  
> Going to provide a pullrequest on GitHub.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to