[
https://issues.jboss.org/browse/ISPN-1792?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-1792:
-------------------------------------
It's not that we need the timestamp to be negative for immortal entries, it is just
that our internal structures are optimised and the InternalCacheEntry implementation used
for immortal entries doesn't have a timestamp field. Saves a long per entry.
If the application needs this, I suggest adding this as a part of your value object.
API to return modification timestamp of a given entry
-----------------------------------------------------
Key: ISPN-1792
URL:
https://issues.jboss.org/browse/ISPN-1792
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 5.1.0.FINAL
Reporter: Thomas Fromm
Assignee: Manik Surtani
Fix For: 5.2.0.FINAL
To realise things like: programmatic delete last X entries from cache, I need the
modification timestamp of the cache entry. ATM I store it inside the key object (cause I
cannot modify value objects) and have my own index on this.
Getting the modification timestamp using the advanced cache api would be really nice.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira