[
https://issues.apache.org/jira/browse/JENA-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053392#comment-15053392
]
ASF GitHub Bot commented on JENA-1085:
--------------------------------------
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/107#issuecomment-164023587
Yes, I think that renaming `writeLock` makes sense. The alternative would
be to actually check the type of transaction and avoid fiddling with that lock
if it is a READ. I think either is okay and either is clearer than what is
there now.
> Review trasnaction 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)
