[jira] [Assigned] (IGNITE-28981) [doc] Document Calcite SELECT FOR UPDATE support

["Dmitry Pavlov (Jira)" <ji...@apache.org>]

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

Dmitry Pavlov reassigned IGNITE-28981:
--------------------------------------

    Assignee: Ignite TC Bot

> [doc] Document Calcite SELECT FOR UPDATE support
> ------------------------------------------------
>
>                 Key: IGNITE-28981
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28981
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>            Reporter: Ignite TC Bot
>            Assignee: Ignite TC Bot
>            Priority: Major
>              Labels: ignite-2, sql
>             Fix For: 2.19
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> IGNITE-28724 added support for SELECT ... FOR UPDATE in the Calcite-based SQL engine.
> The documentation should update docs/_docs/SQL/sql-calcite.adoc under Transaction-aware Queries / SELECT ... FOR UPDATE. The current page still says the statement is not supported.
> Minimal scope:
> * Document that SELECT ... FOR UPDATE is supported inside a PESSIMISTIC transaction.
> * Document the basic syntax, FOR UPDATE OF, NOWAIT, and WAIT n.
> * Mention that without OF all participating cache-based tables are locked; with OF only the tables owning listed columns are locked.
> * Mention the narrow limitations verified by implementation/tests: plain SELECT over cache-based tables and joins; not DISTINCT, GROUP BY, HAVING, aggregate-only result sets, system views, or table functions.
> Source issue: IGNITE-28724
> Implementation PR: https://github.com/apache/ignite/pull/13366
> Merged commit: 009946c769d4b4b7d9a792a85d66b54f4e7afe3d



--
This message was sent by Atlassian Jira
(v8.20.10#820010)