tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stephen mallette (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TINKERPOP-800) [Proposal] Domain/Range checking during traversal construction.
Date Wed, 07 Aug 2019 15:09:00 GMT

     [ https://issues.apache.org/jira/browse/TINKERPOP-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stephen mallette closed TINKERPOP-800.
--------------------------------------
    Resolution: Later

> [Proposal] Domain/Range checking during traversal construction.
> ---------------------------------------------------------------
>
>                 Key: TINKERPOP-800
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-800
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.2-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>            Priority: Major
>              Labels: breaking
>
> I think we should add two new methods to {{Step}}.
> {code}
> Step.getDomain() -> Class
> Step.getRange() -> Class
> {code}
> Now, when someone does:
> {code}
> g.V().out()
> {code}
> {{GraphStep}} will report that its range is {{Vertex.class}}. {{VertexStep}} will report
its domain to be {{Vertex.class}}. Good. No typing issues. However, when you do this:
> {code}
> g.E().out()
> {code}
> {{GraphStep}} will report that its range is {{Edge.class}}. {{VertexStep}} will report
its domain to be {{Vertex.class}} --- {{IllegalArgumentException: "The provided traversal
has an illegal function composition."}}.
> Why is this good -- much better than getting random {{ClassCastExceptions}} at execution
time.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message