[
https://issues.apache.org/jira/browse/TINKERPOP-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239694#comment-17239694
]
Marc de Lignie commented on TINKERPOP-2473:
-------------------------------------------
Yes, indeed, "must-be-present" is close to "must-not-be-removed". You are also
right about the workaround, although the Gremlin Server docs now describe
"implicit", "passive" and "active" authorization strategies, where the implicit
one does not use the Authorizer interface but relies on restricting traversal
strategies that can not be removed or replaced. So, it is does not seem
consistent to release an Authorizer feature without resolving
TINKERPOP-2473/TINKERPOP-669.
> 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)
