You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Artem Budnikov (JIRA)" <ji...@apache.org> on 2018/10/31 09:27:00 UTC

[jira] [Commented] (IGNITE-9763) MVCC: Document TX updates visibility changes for continuous queries.

    [ https://issues.apache.org/jira/browse/IGNITE-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669814#comment-16669814 ] 

Artem Budnikov commented on IGNITE-9763:
----------------------------------------

[~rkondakov] 

I added the information on using continuous queries with MVCC here: [https://apacheignite-sql.readme.io/v2.6/docs/multiversion-concurrency-control#section-continuous-queries]

Please review.

> MVCC: Document TX updates visibility changes for continuous queries.
> --------------------------------------------------------------------
>
>                 Key: IGNITE-9763
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9763
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation, mvcc
>            Reporter: Roman Kondakov
>            Assignee: Artem Budnikov
>            Priority: Major
>             Fix For: 2.7
>
>
> We should document visibility behaviour changes for MVCC transactions in Continuous Queries context: when MVCC transaction completes, it's updates are not visible immediately for the new transaction even they are started in continuous query listener. This is caused by the lag between transaction completes on the node and mvcc coordinator removes this transaction from the active list. Therefore all transactions started during this little time gap between these events will see just completed transaction as active in their snapshot, and, consequently, can't observe it's updates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)