Re: PathRetractionStrategy and TraverserRequirement.PATH

Hello Pieter, There was a bug in RepeatStep OLAP around emit().as(‘x’) that was fixed in 3.2.3. Perhaps it is related… Marko. http://markorodriguez.com > On Oct 26, 2016, at 3:44 AM, pieter-gmail wrote: > > Thanks, now I know Sqlg has indeed been bugged. I am

Re: PathRetractionStrategy and TraverserRequirement.PATH

Thanks, now I know Sqlg has indeed been bugged. I am loosing the label after the emit().as("b"). Cheers Pieter On 25/10/2016 21:29, Marko Rodriguez wrote: > Here is a simple test. Remove PathRetractionStrategy from TinkerGraph > traversal and see what you get? Do you get what Sqlg returns or

Re: PathRetractionStrategy and TraverserRequirement.PATH

Here is a simple test. Remove PathRetractionStrategy from TinkerGraph traversal and see what you get? Do you get what Sqlg returns or the same as if with PathRetractionStrategy. E.g. graph = TinkerFactory.createModern(); g = graph.traversal().withoutStrategies(PathRetractionStrategy.class);

Re: PathRetractionStrategy and TraverserRequirement.PATH

Ok apologies. I thought I spotted the difference and simplified the gremlin too much to highlight what I thought I saw. The above mentioned queries are returning the same result in Sqlg as TinkerGraph. Here is what is not working. final TinkerGraph g = TinkerFactory.createModern();

Re: PathRetractionStrategy and TraverserRequirement.PATH

Hi Pieter, What are the two answers --- TinkerGraph and Sqlg for the respective test traversal? (I suspect the test is bad because group() pushes traversers through with bulks and all so the test might just add to a collection without adding respecting bulks. Probably should change that test