[
https://issues.apache.org/jira/browse/TINKERPOP-2222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-2222.
---------------------------------------
Resolution: Won't Do
Given that no one has shown much interest in this issue, I think we will leave
sandboxing as-is and leave it to providers to produce better security measures.
I think that advancing sandboxing in TinkerPop also doesn't fit well with the
future roadmap where we no longer have scripts.
> Improve sandbox to avoid GraphTraversal casts
> ---------------------------------------------
>
> Key: TINKERPOP-2222
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2222
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.3.6
> Reporter: Stephen Mallette
> Priority: Minor
>
> We have the unfortunate situation where sandboxing makes writing Gremlin a
> bit ugly at times:
> {code}
> gremlin> :>
> g.V().has('person','name','marko').as('m').constant('x').as('l').addE(select('l')).from(select('m')).to('m')
> Script8.groovy: 1: [Static type checking] - Cannot call
> org.apache.tinkerpop.gremlin.process.traversal.dsl.graph.GraphTraversal
> <org.apache.tinkerpop.gremlin.structure.Vertex,
> java.lang.String>#addE(org.apache.tinkerpop.gremlin.process.traversal.Traversal
> <java.lang.Object extends java.lang.Object, java.lang.String>) with
> arguments
> [org.apache.tinkerpop.gremlin.process.traversal.dsl.graph.GraphTraversal <A
> extends java.lang.Object, B extends java.lang.Object>]
> @ line 1, column 1.
>
> g.V().has('person','name','marko').as('m').constant('x').as('l').addE(select('l')).from(select('m')).to('m')
> ^
> 1 error
> Type ':help' or ':h' for help.
> Display stack trace? [yN]n
> gremlin> :>
> g.V().has('person','name','marko').as('m').constant('x').as('l').addE((GraphTraversal<Object,String>)select('l')).from(select('m')).to('m')
> ==>e[3][0-x->0]
> {code}
> The inclusion of type checking forces casts like the one shown above which is
> a bit of an inconvenience. Would be nice if that explicit casting could be
> avoided at least when dealing with a {{GraphTraversal}} object.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
