[ https://issues.apache.org/jira/browse/IGNITE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov reassigned IGNITE-6937: --------------------------------------- Assignee: Vladimir Ozerov (was: Alexander Paschenko) > SQL TX: Support SELECT FOR UPDATE > --------------------------------- > > Key: IGNITE-6937 > URL: https://issues.apache.org/jira/browse/IGNITE-6937 > Project: Ignite > Issue Type: Task > Components: cache, sql > Reporter: Vladimir Ozerov > Assignee: Vladimir Ozerov > Priority: Major > Labels: iep-3 > Fix For: 2.6 > > > Normally in SQL world readers do not block writers. This is how our SELECT > operations should work by default. But we need to add a support for {{SELECT > ... FOR UPDATE}} read mode, when reader obtains exclusive lock on read. > In this mode we lock entries as usual, but then send data back to the caller. > First page can be returned directly in our {{LockResponse}}. Next pages > should be requested in separate requests. With this approach {{SELECT ,,, FOR > UPDATE}} will require only single round-trip to both lock and read data in > case of small updates. > Update {{SELECT}} statement syntax once this feature is supported: > https://apacheignite-sql.readme.io/docs/select -- This message was sent by Atlassian JIRA (v7.6.3#76005)