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-2193) Allow a Traversal to know what TraversalSource it spawned from
Date Tue, 16 Apr 2019 16:31:00 GMT

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

stephen mallette closed TINKERPOP-2193.
---------------------------------------
       Resolution: Done
    Fix Version/s: 3.4.2

> Allow a Traversal to know what TraversalSource it spawned from
> --------------------------------------------------------------
>
>                 Key: TINKERPOP-2193
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2193
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.4.1
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Major
>             Fix For: 3.4.2
>
>
> It's odd that a {{Traversal}} has no knowledge of the {{TraversalSource}} it spawned
from. I say "odd" because:
> 1. we pass the {{TraversalSource}} to the {{Traversal}} on construction only to extract
information from it and then throw it away
> 2. one of the data points we do grab is the {{Graph}} instance of the {{TraversalSource}}
and for some reason we keep that around for the purpose of sometime spawning more {{TraversalSource}}
instances in other components.
> I'm not sure if there was a reason for not keeping the {{TraversalSource}} at some point,
but I'm going to add it and see what happens. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message