[
https://issues.apache.org/jira/browse/JENA-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055919#comment-15055919
]
ASF GitHub Bot commented on JENA-1085:
--------------------------------------
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/108#issuecomment-164425274
`latch` is a very database name and also it is separately used for locks
that have two states e.g. java's `CountDownLatch`.
Shall we call the `writeLock` the `transactionLock`? It makes more sense to
me as it's held for the lifetime of the whole transaction. The name reflects
the implementation as MR+SW. If this is a framework, maybe that would be a
different policy.
> 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)
