[
https://issues.jboss.org/browse/ISPN-3640?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-3640:
----------------------------------------
There's quite a few benefits on this:
* It allows you to store multiple types in the same cache in a type-safe way.
* It would allow for queries on different types to work with a single cache (currently
queries can only be executed on a single cache).
* For transactional caches, it'd be more performant to have a single cache with
multiple types, that a cache for each type and get them to cooperate on the same
transaction.
* Filtering applied by cache view could be done earlier on in the stack that any filtering
that is applied at the cache listener level.
* Iteration would need some work to make sure that it only iterates over entries that pass
the filter.
Extend KeyFilter facility to the whole cache
--------------------------------------------
Key: ISPN-3640
URL:
https://issues.jboss.org/browse/ISPN-3640
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 6.0.0.CR1
Reporter: Paul Ferraro
Assignee: Mircea Markus
The key filter facility is very convenient for users who have multiple key types in the
same cache. It would be very handy if this feature were extended to the whole cache.
e.g.
Cache<?, ?> cache = ...;
KeyFilter filter = ...;
Cache<K, V> view = cache.filter(filter);
view.addListener(listener) // Equivalent to the current cache.addListener(listener,
filter) method
for (Map.Entry<K, V> entry: view.entrySet()) {
...
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira