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

Kelvin R. Lawrence commented on TINKERPOP-2172:
-----------------------------------------------

I'm not quite sure from the fix version and reported version above. Did this 
fix make the 3.4.1 release? It still seems to be failing at that level for me. 
Cheers, Kelvin.

> PartitionStrategy doesn't apply to AddEdgeStartStep
> ---------------------------------------------------
>
>                 Key: TINKERPOP-2172
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2172
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.4.1
>            Reporter: Vladimir
>            Assignee: stephen mallette
>            Priority: Major
>             Fix For: 3.3.6, 3.4.1
>
>
> PartitionStrategy doesn't apply to traversal started with addE step.
> For instance:
> PartitionStrategy partitionStrategy = PartitionStrategy.build()
>  
> .partitionKey({color:#660e7a}partition{color}).writePartition({color:#008000}"A"{color}).readPartitions({color:#008000}"A"{color}).create();
>  GraphTraversalSource source = 
> {color:#660e7a}g{color}.withStrategies(partitionStrategy);
>  Vertex v1 = source.addV().property({color:#008000}"any"{color}, 
> {color:#008000}"thing"{color}).next();
>  Vertex v2 = source.addV().property({color:#008000}"some"{color}, 
> {color:#008000}"thing"{color}).next();
>  Edge e1 = source.withSideEffect({color:#008000}"v2"{color}, 
> v2).V(v1.id()).addE({color:#008000}"connectsTo"{color}).from({color:#008000}"v2"{color}).property({color:#008000}"every"{color},
>  {color:#008000}"thing"{color}).next();
>  Edge e2 = 
> source.addE({color:#008000}"relatesTo"{color}).from(v2).to(v1).property({color:#008000}"every"{color},
>  {color:#008000}"thing"{color}).next();
> If you check e1 you will see partition property. But edge e2 wont have any 
> partition property.



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

Reply via email to