[
https://issues.apache.org/jira/browse/IGNITE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4134:
--------------------------------
Description:
There are two things to pay attention to right now:
- It's not possible to set an expiration policy globally for a cache at the
level of C# config and App.config.
- It's not clear that {{null}} should be used if the one wants to set eternal
expiration. This has to be documented.
was:
There are two things to pay attention to right now:
- It's not possible to set an expiration policy globally for a cache at the
level of C# and App.config.
- It's not clear that {{null}} should be used if the one wants to set eternal
expiration. This has to be documented.
> .NET: Expiration policy related improvements
> --------------------------------------------
>
> Key: IGNITE-4134
> URL: https://issues.apache.org/jira/browse/IGNITE-4134
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
> Reporter: Denis Magda
> Fix For: 1.8
>
>
> There are two things to pay attention to right now:
> - It's not possible to set an expiration policy globally for a cache at the
> level of C# config and App.config.
>
> - It's not clear that {{null}} should be used if the one wants to set eternal
> expiration. This has to be documented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
