You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/03/13 16:23:00 UTC

[jira] [Commented] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

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

Ignite TC Bot commented on IGNITE-10663:
----------------------------------------

{panel:title=-&gt; Run :: IntelliJ IDEA Inspections: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-&gt; Run :: IntelliJ IDEA Inspections* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3305183&amp;buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]

> Implement cache mode allows reads with consistency check and fix
> ----------------------------------------------------------------
>
>                 Key: IGNITE-10663
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10663
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>              Labels: iep-31
>             Fix For: 2.8
>
>
> The main idea is to provide special "read from cache" mode which will read a value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate strategy.
> ToDo list:
> 1) {{cache.withConsistency().get(key)}} should guarantee values will be checked across the topology and fixed if necessary.
> 2) LWW (Last Write Wins) strategy should be used for validation.
> 3) Since  LWW and any other strategy do not guarantee that the correct value will be chosen.
> We have to record the event contains all values and the chosen one.



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