You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Rakov (Jira)" <ji...@apache.org> on 2020/07/03 12:22:00 UTC

[jira] [Updated] (IGNITE-13211) Improve public exceptions for case when user attempts to access data from a lost partition

     [ https://issues.apache.org/jira/browse/IGNITE-13211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Rakov updated IGNITE-13211:
--------------------------------
    Description: 
After IGNITE-13003, attempt to access lost partition from public API throws CacheException with CacheInvalidStateException inside as a root cause. We can improve user experience a bit:
1. Create new type of public exception (subclass of CacheException), which will be thrown in scenarios when we access lost data
2. In case partition is lost in persistent cache, error message should be changed from "partition data has been lost" to "partition data temporary unavailable".

  was:
After IGNITE-13003, attempt to access lost partition from public API throws CacheException with CacheInvalidStateException inside as a root cause. We can improve user experience a bit:
1. Create new type of public exception (subclass of CacheException), which will be thrown in accessing lost data scenarios
2. In case partition is lost in persistent cache, error message should be changed from "partition data has been lost" to "partition data temporary unavailable".


> Improve public exceptions for case when user attempts to access data from a lost partition
> ------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13211
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13211
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Rakov
>            Priority: Major
>
> After IGNITE-13003, attempt to access lost partition from public API throws CacheException with CacheInvalidStateException inside as a root cause. We can improve user experience a bit:
> 1. Create new type of public exception (subclass of CacheException), which will be thrown in scenarios when we access lost data
> 2. In case partition is lost in persistent cache, error message should be changed from "partition data has been lost" to "partition data temporary unavailable".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)