[ https://issues.apache.org/jira/browse/TRAFODION-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285000#comment-16285000 ]
ASF GitHub Bot commented on TRAFODION-2834: ------------------------------------------- GitHub user anoopsharma00 opened a pull request: https://github.com/apache/incubator-trafodion/pull/1333 JIRA TRAFODION-2834 Streamline supported xn access modes More details in jira. traf DTM only supports 'read committed access' for selects and 'set transaction ' stmts. With this checkin, only those 2 options will be allowed. All other access options will return an error. Read uncommitted access will be treated as read committed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/anoopsharma00/incubator-trafodion ansharma_traf_xn_deliver_br Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/1333.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1333 ---- commit 6dd81240697f689ce26b93021d17d4f602044c77 Author: Anoop Sharma <anoop.sha...@esgyn.com> Date: 2017-12-09T21:18:13Z JIRA TRAFODION-2834 Streamline supported xn access modes traf DTM only supports 'read committed access' for selects and 'set transaction ' stmts. With this checkin, only those 2 options will be allowed. All other access options will return an error. Read uncommitted access will be treated as read committed. ---- > 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)