[
https://issues.apache.org/jira/browse/TINKERPOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120704#comment-18120704
]
ASF GitHub Bot commented on TINKERPOP-3282:
-------------------------------------------
spmallette commented on PR #3639:
URL: https://github.com/apache/tinkerpop/pull/3639#issuecomment-5889098083
@kenhuuu
> So lock contention was already going to be a problem before, but this
current design requires you hold these locks for even longer.
I had to make a decision around this early on and decided that for this
first effort it would be acceptable to take these limitations around locking to
at least cover the current use of TinkerGraph as typically in-memory with a
single writer - there are still many production use cases for that type of
operation. I wanted this round of work to at least satisfy that case without
also making this a transaction refactoring on top of that. As you call this
out, I sense that not enough has been written in the docs to be clear about the
limitation and where TinkerStorageGraph is best used.
> TinkerGraph file persistence
> ----------------------------
>
> Key: TINKERPOP-3282
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3282
> Project: TinkerPop
> Issue Type: Improvement
> Components: tinkergraph
> Affects Versions: 3.7.6
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
>
> Give TinkerGraph a basic file persistence option tied to its transactional
> usage so that it can support some more complex use cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
