[JBoss JIRA] (ISPN-9966) Guidelines for evolving the API over time
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9966?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9966:
-------------------------------
Fix Version/s: 10.0.0.CR3
> Guidelines for evolving the API over time
> -----------------------------------------
>
> Key: ISPN-9966
> URL: https://issues.jboss.org/browse/ISPN-9966
> Project: Infinispan
> Issue Type: Sub-task
> Components: API
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> A plan on how we plan to evolve APIs over time.
> * What recommendations should developers follow when they want to add/change/remove API methods?
> * At which point they should come up with new interfaces and how do users migrate from one to the other?
> * When should we create new modules? When can we reuse existing API modules?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-9966) Guidelines for evolving the API over time
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9966?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-9966.
--------------------------------
Resolution: Done
> Guidelines for evolving the API over time
> -----------------------------------------
>
> Key: ISPN-9966
> URL: https://issues.jboss.org/browse/ISPN-9966
> Project: Infinispan
> Issue Type: Sub-task
> Components: API
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Major
>
> A plan on how we plan to evolve APIs over time.
> * What recommendations should developers follow when they want to add/change/remove API methods?
> * At which point they should come up with new interfaces and how do users migrate from one to the other?
> * When should we create new modules? When can we reuse existing API modules?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence
by Pedro Ruivo (Jira)
[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ]
Pedro Ruivo commented on ISPN-10618:
------------------------------------
PR for 10.0 integrated!
> If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10618
> URL: https://issues.jboss.org/browse/ISPN-10618
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.0.CR2
> Environment: Cache configuration with preload
> <local-cache name="default">
> <persistence>
> <file-store shared="false" preload="true" fetch-state="true"/>
> </persistence>
> </local-cache>
> Reporter: Wolf-Dieter Fink
> Assignee: Will Burns
> Priority: Blocker
> Fix For: 10.0.0.CR3, 9.4.17.Final
>
>
> If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration.
> This works correct if the server is not restarted or preload=false for the store.
> If preload is enabled and the server preload the date the creationTime is set to the current server start time.
> In this case all expiration for existing entries is not working correctly
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months