[
https://issues.apache.org/jira/browse/TINKERPOP-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Hockmann closed TINKERPOP-3066.
---------------------------------------
Resolution: Not A Problem
I'm closing this as its mostly a usage question for now and you also asked this
on the users mailing list which is a better place to discuss this question and
determine whether this is actually expected behavior or a bug:
https://groups.google.com/g/gremlin-users/c/Hnjp8UqJ2RU
If it's indeed a bug, then we can still create an issue here and provide a
clear description of what the expected behavior is vs the actual behavior.
> Different behaviors when adding "dedup()"
> -----------------------------------------
>
> Key: TINKERPOP-3066
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3066
> Project: TinkerPop
> Issue Type: Bug
> Components: gremlint
> Affects Versions: 3.7.0
> Environment: Windows 10
> Reporter: Junhao lan
> Priority: Major
>
> I think the traversal is really weird.
> * first traversal: {{g.addV().addV().limit(0)}} -> creates 1 vertex
> * second traversal: {{g.addV().addV().dedup().limit(0)}} -> creates 2
> vertices
> And {{limit(0)}} is also strange and I don't really know what the expected
> behavior should be here with Gremlin.Maybe there is a bug?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
