Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-2473

Prevent TraversalStrategy instances of the same type to be added to a TraversalSource

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.4.8
    • Fix Version/s: 3.5.0
    • Component/s: process
    • Labels:
      None

      Description

      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).

        Attachments

          Activity

            People

            • Assignee:
              spmallette Stephen Mallette
              Reporter:
              spmallette Stephen Mallette

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment