Ah, ok thanks for clarifying. I will leave my ticket unassigned
ср, 31 мая 2017 г. в 21:10, Alexey Goncharuk :
> Aleksey,
>
> Generally, this decision cannot be made on a single node because a
> transaction may affect multiple nodes, and one node may have already
> committed the transaction and t
Aleksey,
Generally, this decision cannot be made on a single node because a
transaction may affect multiple nodes, and one node may have already
committed the transaction and the other - not. There is a dependant ticket
in the ticket you are currently working on which will cover all the caes.
Mea
one possible solution is to lock entry reading section while userCommit()
method is executing.
ср, 31 мая 2017 г., 16:52 ALEKSEY KUZNETSOV :
> Hi, Igntrs!
> When the first writer thread has commited values and cache entries are
> getting updated with this new values, another thread is getting par
Hi, Igntrs!
When the first writer thread has commited values and cache entries are
getting updated with this new values, another thread is getting partially
assigned values through the
cache.getAll(keys)
should this method wait for all newly updated entries to finish , or should
it throw the exce
simply because it’s named in a meaningless
way like “IGNITE-4809”
—
Denis
> On Apr 6, 2017, at 11:28 AM, ALEKSEY KUZNETSOV
> wrote:
>
> Hi, Igniters! I will take IGNITE-4809
> <https://issues.apache.org/jira/browse/IGNITE-4809> if you dont mind
> --
>
> *
EKSEY KUZNETSOV :
> Hi, Igniters! I will take IGNITE-4809
> <https://issues.apache.org/jira/browse/IGNITE-4809> if you dont mind
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>
Hi, Igniters! I will take IGNITE-4809
<https://issues.apache.org/jira/browse/IGNITE-4809> if you dont mind
--
*Best Regards,*
*Kuznetsov Aleksey*
Andrew Mashenkov created IGNITE-4809:
Summary: Cache.getAll can return partially commited results.
Key: IGNITE-4809
URL: https://issues.apache.org/jira/browse/IGNITE-4809
Project: Ignite
