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/04/30 19:27:06 UTC
[jira] [Closed] (TINKERPOP3-645) Groovy compute tests assume
numeric IDs
[ https://issues.apache.org/jira/browse/TINKERPOP3-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez closed TINKERPOP3-645.
-----------------------------------------
Resolution: Fixed
Assignee: Marko A. Rodriguez
This is fixed. As recommended by [~spmallette], {{TraversalSupplier}} can now take an var args of {{Object...}} which are the bindings. Easy fix. Thanks.
> Groovy compute tests assume numeric IDs
> ---------------------------------------
>
> Key: TINKERPOP3-645
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-645
> Project: TinkerPop 3
> Issue Type: Bug
> Components: test-suite
> Reporter: Bryn Cooke
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.0.GA
>
>
> The groovy compute tests assume that element ids are numeric.
> If they are a sting the following test gives an error:
> {code:java}
> public Traversal<Edge, Edge> get_g_EX7X_hasLabelXknowsX(final Object e7Id) {
> ComputerTestHelper.compute(" g.E(${e7Id}).hasLabel('knows')", g);
> }
> {code}
> Script5.groovy: 1: unexpected token: bk @ line 1, column 11.
> g.E(2e2-3bk-9hx-3cg).hasLabel('knows')
> I expect this would also affect vertices in implementations where IDs are non-numeric.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)