[ 
https://issues.apache.org/jira/browse/JENA-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360463#comment-16360463
 ] 

ASF subversion and git services commented on JENA-1483:
-------------------------------------------------------

Commit 48c6dc64539c4af3427017a656993f5e034728e4 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=48c6dc6 ]

JENA-1483: Merge commit 'refs/pull/355/head' of https://github.com/apache/jena

This closes #355.


> Allow different promote() modes.
> --------------------------------
>
>                 Key: JENA-1483
>                 URL: https://issues.apache.org/jira/browse/JENA-1483
>             Project: Apache Jena
>          Issue Type: Improvement
>            Reporter: Andy Seaborne
>            Priority: Major
>
> This follows on from JENA-1458.
> In the previous work, there is one promote operation, {{promote()}}, that 
> takes the transaction type to determine whether to promote with or without 
> "read commits" effects.
> This ticket introduces {{promote(Promote mode)}} where the mode can be given 
> explicitly.
> {{promote()}} becomes a default method of the interface that chooses the 
> promote mode based on the way the transaction was started.
> This ticket also changes {{promote}} to return boolean false, and  leave the 
> transaction still valid, if an attempt is made to promote a read-only 
> transaction. This is more uniform between the transaction type and any 
> intermediate writer blocking promotion in READ_PROMOTE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to