[
https://issues.apache.org/jira/browse/JENA-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1483.
---------------------------------
Resolution: Done
Assignee: Andy Seaborne
Fix Version/s: Jena 3.7.0
> 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
> Assignee: Andy Seaborne
> Priority: Major
> Fix For: Jena 3.7.0
>
>
> 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)
