[
https://issues.apache.org/jira/browse/JENA-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055931#comment-15055931
]
ASF GitHub Bot commented on JENA-1085:
--------------------------------------
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/108#issuecomment-164426433
That might be a good idea. If I understand correctly where you're taking
this, we have a lock that must be acquired to change transactional state (for
example, to commit) but can be released as soon as that is accomplished
(`systemLock`) and a lock that must be held as long as a transaction is in
progress (`writeLock`). `transactionLock` does sound like a better name for the
latter, especially since it's held by readers, too.
> Review transaction finishes for DatasetGraphInMemory
> ----------------------------------------------------
>
> Key: JENA-1085
> URL: https://issues.apache.org/jira/browse/JENA-1085
> Project: Apache Jena
> Issue Type: Task
> Components: ARQ
> Affects Versions: Jena 3.0.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 3.1.0
>
>
> This JIRA is for a review of the transaction finishing code.
> Some of the code works because of the nature of specific implementations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
