[
https://issues.apache.org/jira/browse/IGNITE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-4927:
-------------------------------------
Description:
Currently, the write-behind store is backed by a map, therefore when several
updates come to the same key, they are coalesced.
We need to introduce optional mode and back write-behind with a queue and pass
each <k, v> to a database.
was:
Currently write behind store is backed by a map, therefore when several updates
come to the same key its values' change history is lost.
We need to introduce optional mode and back write behind with a queue and pass
each <k, v> to database.
> Write behind - need new mode without skipping values history
> ------------------------------------------------------------
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
> Issue Type: Improvement
> Reporter: Yakov Zhdanov
> Assignee: Alexey Dmitriev
>
> Currently, the write-behind store is backed by a map, therefore when several
> updates come to the same key, they are coalesced.
> We need to introduce optional mode and back write-behind with a queue and
> pass each <k, v> to a database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
