[
https://issues.apache.org/jira/browse/TINKERPOP3-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560002#comment-14560002
]
Dylan Millikin commented on TINKERPOP3-704:
-------------------------------------------
I don't think getting temporary ids is abnormal. If anything it's most likely a
requirement as you would probably want to continue running queries against the
transaction using that ID.
For other cases... Well, when accessing the db remotely, temporary ids are
going to be a pain to handle anyways. You're going to have to manage it on your
app layer, I don't think there's any way around it. I'm sure some information
around these user cases can be found for orientDb.
I think this is tricky because the documentation encourages users to use the
simpler yet "incorrect" un-iterated form for queries. It quickly becomes
confusing.
I'm all for supporting iteration in the same thread as the script evaluation.
As of today our lower level tests are all passing but we'll need to run the
tinkergraph based tests against titan (ie: rewrite some of them) because
there's no guaranty they'll work in a transactional graph (maybe we forgot some
iterations and tinkergraph tests don't reflect that our queries are incorrect).
> Better Encapsulate Gremlin Server Requests Around Transactions
> --------------------------------------------------------------
>
> Key: TINKERPOP3-704
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-704
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: server
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.0.0.GA
>
>
> See:
> https://github.com/thinkaurelius/titan/issues/1095
> for more information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
