[PR] TINKERPOP-3298 TinkerTransactionGraph issue with index loopup and kept references [tinkerpop]

["spmallette (via GitHub)" <gi...@apache.org>]

spmallette opened a new pull request, #3728:
URL: https://github.com/apache/tinkerpop/pull/3728

    https://issues.apache.org/jira/browse/TINKERPOP-3298
   
   In TinkerTransactionGraph, an element found through an index, or a reference kept across a commit, was the committed element itself rather than a copy belonging to the transaction. A write through it changed committed state directly: other transactions could see it before commit, rollback didn't undo it, and concurrent writers could fail with ArrayIndexOutOfBoundsException.
   
   - Index lookups now return the transaction's own copy, as vertices(id) already does.
   - Commit stores a copy of the transaction's version as the committed element, so a reference kept by the caller is never committed state.
   - Writing through a kept reference to a vertex or edge deleted since then still throws ... was removed, as before.
   
    VOTE +1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@tinkerpop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] TINKERPOP-3298 TinkerTransactionGraph issue with index lookup and kept references [tinkerpop]

["spmallette (via GitHub)" <gi...@apache.org>]

spmallette merged PR #3728:
URL: https://github.com/apache/tinkerpop/pull/3728


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@tinkerpop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org