[ 
https://issues.apache.org/jira/browse/TINKERPOP3-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP3-661.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0.GA
         Assignee: stephen mallette

So hard to make sure stuff runs right without a Graph that doesn't support 
{{userSuppliedIds}}.  Makes me wonder if we can't create an {{idManager}} for 
TinkerGraph that works that way so that we can validate more of the tests suite 
before it gets into the wild (then we only have transactions left uncovered as 
opposed to all this id related stuff which is a lot).

Anyway, fixed as of: 
https://github.com/apache/incubator-tinkerpop/commit/8e9871d2f9d9e5dbc3dcd3f35bea52cb95c58232

Guess we need to stamp out a new version....weak.

> Gryo reader not working with supportsUserSuppliedIds 'false'
> ------------------------------------------------------------
>
>                 Key: TINKERPOP3-661
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-661
>             Project: TinkerPop 3
>          Issue Type: Bug
>          Components: structure
>            Reporter: Bryn Cooke
>            Assignee: stephen mallette
>             Fix For: 3.0.0.GA
>
>
> When edges are added to the graph they will always create new vertices for 
> each side of the edge rather than using the vertices that have been created 
> in the previous phase of the read.
> The problem is at:
> https://github.com/apache/incubator-tinkerpop/blob/master/gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/structure/util/Attachable.java#L295
> The edge needs to somehow use the vertex cache:
> https://github.com/apache/incubator-tinkerpop/blob/master/gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/structure/io/gryo/GryoReader.java#L82
> to give us the correct vertices.
> This probably affects other reader implementations as well.



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

Reply via email to