ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Paschenko (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-6937) SQL TX: Support SELECT FOR UPDATE
Date Thu, 07 Dec 2017 17:47:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alexander Paschenko reassigned IGNITE-6937:

    Assignee: Alexander Paschenko

> ---------------------------------
>                 Key: IGNITE-6937
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6937
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, sql
>            Reporter: Vladimir Ozerov
>            Assignee: Alexander Paschenko
>              Labels: iep-3
>             Fix For: 2.4
> 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

View raw message