ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atri Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1059) putAll() throws IgniteException instead of CachePartialUpdateException in ascyn mode when partial update occurs.
Date Mon, 29 Jun 2015 12:45:04 GMT

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

Atri Sharma commented on IGNITE-1059:
-------------------------------------

Was thinking of looking into internals with this one.

If you dont mind, please advice with more details and advice on how to tackle this.


> putAll() throws IgniteException instead of CachePartialUpdateException in ascyn mode
when partial update occurs.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-1059
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1059
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Atri Sharma
>            Priority: Critical
>             Fix For: sprint-7
>
>
> Problem:
> When partial update occurs in sync mode, user receive CachePartialUpdateException as
expected, which he can use to obtain failed key and re-process them.
> But if it occurs in async mode, future.get() throws IgniteException with nested  CachePartialUpdateCheckedException.
> Expected behavior after fix:
> future.get() throws CachePartialUpdateException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message