Daniel Weber created TINKERPOP-3222:
---------------------------------------

             Summary: ReservedKeysVerificationStrategy verification fails when 
the invalid AddPropertyStep has an explicit cardinality set
                 Key: TINKERPOP-3222
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3222
             Project: TinkerPop
          Issue Type: Bug
          Components: process
    Affects Versions: 3.7.5, 3.8.0
         Environment: Gremlin Console, Windows 11
GremlinServer Docker container. 
            Reporter: Daniel Weber


Setup:

{{g=TinkerGraph.open().traversal().withStrategies(ReservedKeysVerificationStrategy.build().throwException().create())}}

The query

{{g.addV().property('id', 'someId')}}

fails correctly because "The provided traversal contains a AddVertexStartStep 
that is setting a property key to a reserved word: id". However:

{{g.addV().property(single, 'id', 'someId')}}

does not and neither do

{{g.addV().property(list, 'id', 'someId'), g.addV().property(set, 'id', 
'someId')}}

So an explicitly set cardinality lets the ReservedKeysVerificationStrategy miss 
property additions with restricted property names.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to