[
https://issues.apache.org/jira/browse/TINKERPOP-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236644#comment-17236644
]
Marc de Lignie edited comment on TINKERPOP-2473 at 11/21/20, 11:32 AM:
-----------------------------------------------------------------------
Another indication that some action is needed regarding multiple additions of
the same strategy is the inconsistency in behavior. While SubgraphStrategy has
superseding semantics (the last added Strategy takes precedence) the
PartionStrategy has ignore semantics (the first added Strategy takes
precedence). So, looking back it would have been better to just throw an error
as default behavior. In the present stage, though, this would be a breaking
change.
was (Author: hadoopmarc):
Another indication that some action is needed regarding multiple additions of
the same strategy is the inconsistency in behaviour. While SubgraphStrategy has
superseding semantics (the last added Strategy takes precedence) the
PartionStrategy has ignore semantics (the first added Strategy takes
precedence). So, looking back it would have been to just throw an error as
default behavior. In the present stage, though, this would be a breaking change.
> 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)
