You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Anoop Sharma (JIRA)" <ji...@apache.org> on 2017/12/08 22:16:00 UTC
[jira] [Work started] (TRAFODION-2834) Streamline supported xn
access modes
[ https://issues.apache.org/jira/browse/TRAFODION-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on TRAFODION-2834 started by Anoop Sharma.
-----------------------------------------------
> Streamline supported xn access modes
> ------------------------------------
>
> Key: TRAFODION-2834
> URL: https://issues.apache.org/jira/browse/TRAFODION-2834
> Project: Apache Trafodion
> Issue Type: Improvement
> Reporter: Anoop Sharma
> Assignee: Anoop Sharma
>
> Current traf code allows for the following xn modes in select queries:
> 1. for browse access
> 2. for stable access
> 3. for repeatable access
> 4. repeatable read access
> 5. for repeatable read access
> 6. serializable access
> 7. for serializable access
> 8. read uncommitted access
> 9. for read uncommitted access
> 10. read committed access
> 11. for read committed access
> Internally, the only supported mode is ‘read committed+’ (slightly more than true read committed).
> In addition, ‘set transaction isolation level <mode>’ currently allows for #4, #6, #8, #10.
> Proposal:
> Remove #1, #2, #3 as these are leftover options from previous product.
> Return syntax error.
> Return unsupported option error if #4, #5, #6, #7 are specified
> as traf currently does not support repeatable or serialization functionality
> treat ‘read uncommitted’ as ‘read committed’
> If no mode is specified, then treat it as ‘read committed’
> With this change, only those modes that are internally supported will be allowed.
> If we do support some modes in future (repeatable, serializable), then those restrictions will be lifted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)