You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2017/02/13 13:50:41 UTC
[jira] [Updated] (TINKERPOP-1631) Fix visibility issues with the
BindingsGremlinPlugin
[ https://issues.apache.org/jira/browse/TINKERPOP-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette updated TINKERPOP-1631:
----------------------------------------
Fix Version/s: 3.2.5
> Fix visibility issues with the BindingsGremlinPlugin
> ----------------------------------------------------
>
> Key: TINKERPOP-1631
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1631
> Project: TinkerPop
> Issue Type: Improvement
> Components: plugin
> Affects Versions: 3.2.3
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.2.5
>
>
> The whole aspect of applying bindings via plugin with the revised plugin system is a little sketchy/inconsistent.
> * Bindings should always be assigned to global scope because engine scope is always overriden with local bindings.
> * Bindings assigned by {{HadoopGremlinPlugin}} don't seem to want to appear in Gremlin Server.
> * There needs to be some form of mock {{GremlinScriptEngine}} that can be used to test plugins without having to depend on an actual implementation
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)