You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/03 16:02:04 UTC
[jira] [Commented] (TINKERPOP3-783) asVertex Does Not Always Return
Correct State
[ https://issues.apache.org/jira/browse/TINKERPOP3-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651881#comment-14651881 ]
Marko A. Rodriguez commented on TINKERPOP3-783:
-----------------------------------------------
Is there a test case that you can provide so I know what is failing and can work to solve it?
> asVertex Does Not Always Return Correct State
> ---------------------------------------------
>
> Key: TINKERPOP3-783
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-783
> Project: TinkerPop 3
> Issue Type: Bug
> Components: process
> Affects Versions: 3.0.0-incubating
> Reporter: stephen mallette
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.1-incubating, 3.1.0-incubating
>
>
> In {{AddPropertyStep}} the {{asVertex}} member variable is currently set as follows:
> {code}
> this.asVertex = null != cardinality || this.vertexPropertyKeyValues.length > 0;
> {code}
> which basically means that {{asVertex}} will get the "wrong" value if {{property}} is called like this:
> {code}
> g.V().addV().property("this", "thing")
> {code}
> I would expect {{asVertex}} to return true in this case. This value is relied upon internal to the {{Step}} and by {{TraversalStrategy}} implementations to determine the nature of what the the {{Step}} is processing so it's important that it return properly under this condition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)