You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/12/31 14:11:00 UTC

[jira] [Commented] (TINKERPOP-2473) Allow TraversalStrategy instances to be merged

    [ https://issues.apache.org/jira/browse/TINKERPOP-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257007#comment-17257007 ] 

ASF GitHub Bot commented on TINKERPOP-2473:
-------------------------------------------

spmallette opened a new pull request #1376:
URL: https://github.com/apache/tinkerpop/pull/1376


   https://issues.apache.org/jira/browse/TINKERPOP-2473
   
   Don't think that this is a major change in the sense that it's unlikely that anyone was relying on the old behavior. The code now just better enforces what was expected to happen.
   
   VOTE +1


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Allow TraversalStrategy instances to be merged
> ----------------------------------------------
>
>                 Key: TINKERPOP-2473
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2473
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.4.8
>            Reporter: Stephen Mallette
>            Priority: Major
>
> Not sure if this is a great idea but it came up as part of TINKERPOP-2389 where there might be a need to assign both a client-side and server-side {{SubgraphStrategy}}. Currently, while not explicit, you can't assign more than one strategy of a particular type using {{withStrategies()}}. This task would make that explicit and provide a direct way for mergeable strategies to be pushed together into one. If we did that it would also simplify {{OptionsStrategy}} usage in {{with()}} step which currently finds an existing one first if present and then adds to it (otherwise creates it new). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)