[TINKERPOP-2704] Traversal close() semantics

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.5.2
• Component/s: process
• Assignee: Unassigned
• Reporter: Stephen Mallette
• Created: 16/Feb/22 15:07
• Updated: 27/Sep/23 20:29

Description

For 3.4.13/3.5.2 we added an explicit close state on a Traversal. It wasn't clear though if the close state should only apply to the root traversal. where as child traversals are anonymous and reused the root is not. so are child traversals really closeable? and what power does a reset() have in relation to a close() and this end state? also consider clone() and if the close state should be effectively be reset in that case (that is traditionally how that implementation has worked but it broke in 3.5.2/3.4.13 unfortunately).

Issue Links

• is related to: TINKERPOP-2781 Nested __.or() query causes excessive cpu usage CloseableIterator.closeIterator