[IGNITE-9888] Document MVCC continuous queries

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: documentation
• Ignite Flags: Docs Required
• Assignee: Artem Budnikov
• Reporter: Vladimir Ozerov
• Created: 15/Oct/18 14:52
• Updated: 23/Nov/18 10:47
• Resolved: 23/Nov/18 10:47

Description

Key differences with continuous queries for non-MVCC caches:
1) When event is received, subsequent read of the same key may still return previous value for some time (i.e. no guarantee of happens-before between event and subsequent read)
2) Keys for notification are kept in memory. If transaction is too large, OOME could happen. In order to avoid that, we skip notification of too large transactions.

rkondakov, could you please elaborate on how is this implemented?

Issue Links

• is related to: IGNITE-9763 MVCC: Document TX updates visibility changes for continuous queries.
• relates to: IGNITE-7953 MVCC TX: continuous queries