ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Gura (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-1544) Make sure objects number stored in a cache can be bigger than Integer.MAX_VALUE
Date Wed, 11 Nov 2015 14:15:11 GMT

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

Andrey Gura updated IGNITE-1544:
--------------------------------
    Summary: Make sure objects number stored in a cache can be bigger than Integer.MAX_VALUE
 (was: Make sure objects number stored in a cache can be bigger than Integer.MAX_INT)

> Make sure objects number stored in a cache can be bigger than Integer.MAX_VALUE
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-1544
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1544
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Andrey Gura
>            Priority: Critical
>             Fix For: 1.5
>
>
> Make sure that a cache (partitioned) can actually hold number of objects bigger than
{{Integer.MAX_VALUE}}. Because {{Integer.MAX_VALUE}} is not enough for some life use cases
and business domains.
> At least the following should be done:
> - IgniteCache must return cache size as a {{long}} value;
> - Make sure (make a test) that a partitioned cache can store number of objects much bigger
than {{Integer.MAX_VALUE}};
> - find and edit info regarding this limitation.



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

Mime
View raw message