[
https://issues.apache.org/jira/browse/TINKERPOP-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-930:
---------------------------------------
Description:
The current "tranaction manager" in Gremlin Server is just like Rexster's and
it's not very smart. It makes no distinction about what graphs were actually
affected when it issues its auto-commits/rollbacks at the end of a sessionless
request. For those with a number of different Graph instances configured in
Gremlin Server, that's a lot of extra empty commits if the intent is to just
mutate a single graph in the set. I'm not sure what that time amounts to, but
it seems sensible that if we could only commit when needed then it would be
better than lots of extra commits for nothing.
http://mail-archives.apache.org/mod_mbox/incubator-tinkerpop-dev/201510.mbox/%3CCAA-H438-1qRCbu5RO7-5YCACm3Jk%2B3gTC_w8hk8T2hzdVYoVPA%40mail.gmail.com%3E
Provide a server-side setting that puts Gremlin Server in some form of "strict"
mode (the default) where users must supply one legal set of aliases in order
for the script to be executed. Use that alias to determine what graph to
commit on.
Consider using a namespaced approach as well where a single alias could be
defined as {{graphName}}.{{traversalName}} which would further validate that
the server is committing the right thing.
was:
The current "tranaction manager" in Gremlin Server is just like Rexster's and
it's not very smart. It makes no distinction about what graphs were actually
affected when it issues its auto-commits/rollbacks at the end of a sessionless
request. For those with a number of different Graph instances configured in
Gremlin Server, that's a lot of extra empty commits if the intent is to just
mutate a single graph in the set. I'm not sure what that time amounts to, but
it seems sensible that if we could only commit when needed then it would be
better than lots of extra commits for nothing.
http://mail-archives.apache.org/mod_mbox/incubator-tinkerpop-dev/201510.mbox/%3CCAA-H438-1qRCbu5RO7-5YCACm3Jk%2B3gTC_w8hk8T2hzdVYoVPA%40mail.gmail.com%3E
Provide a server-side setting that puts Gremlin Server in some form of "strict"
mode (the default) where users must supply one legal set of rebindings in order
for the script to be executed. Use that rebinding to determine what graph to
commit on.
Consider using a namespaced approach as well where a single rebinding could be
defined as {{graphName}}.{{traversalName}} which would further validate that
the server is committing the right thing.
> Tie Alias to Transaction Manager in Gremlin Server
> --------------------------------------------------
>
> Key: TINKERPOP-930
> URL: https://issues.apache.org/jira/browse/TINKERPOP-930
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.1.1-incubating
>
>
> The current "tranaction manager" in Gremlin Server is just like Rexster's and
> it's not very smart. It makes no distinction about what graphs were actually
> affected when it issues its auto-commits/rollbacks at the end of a
> sessionless request. For those with a number of different Graph instances
> configured in Gremlin Server, that's a lot of extra empty commits if the
> intent is to just mutate a single graph in the set. I'm not sure what that
> time amounts to, but it seems sensible that if we could only commit when
> needed then it would be better than lots of extra commits for nothing.
> http://mail-archives.apache.org/mod_mbox/incubator-tinkerpop-dev/201510.mbox/%3CCAA-H438-1qRCbu5RO7-5YCACm3Jk%2B3gTC_w8hk8T2hzdVYoVPA%40mail.gmail.com%3E
> Provide a server-side setting that puts Gremlin Server in some form of
> "strict" mode (the default) where users must supply one legal set of aliases
> in order for the script to be executed. Use that alias to determine what
> graph to commit on.
> Consider using a namespaced approach as well where a single alias could be
> defined as {{graphName}}.{{traversalName}} which would further validate that
> the server is committing the right thing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
