[JBoss JIRA] (ISPN-2192) Allow using Distributed Execution against any cache (not just clustered caches)
10:40 p.m.
Randall Hauch created ISPN-2192:
-----------------------------------
Summary: Allow using Distributed Execution against any cache (not just
clustered caches)
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache, regardless
of its configuration. (Ideally, it would be possible for Map-Reduce to also be used
against any cache.)
--
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
10:42 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
SBS JIRA Integration updated ISPN-2192:
---------------------------------------
Forum Reference: https://community.jboss.org/message/588864#588864
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
2:18 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on ISPN-2192:
-------------------------------------------
I do not understand how it makes sense to allow distributed execution for local cache? We
allow Map/Reduce on DIST cache and distributed execution on REPL and DIST.
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
2:31 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Randall Hauch commented on ISPN-2192:
-------------------------------------
Processing all of the entries in the cache currently requires different logic depending
upon the configuration. For example, to use distributed execution on a DIST cache, you do
this:
{code:java}
Cache<K, V> cache = ...
DistributedCallable<K,V,R> callable = ...
DistributedExecutorService distributedExecutor = new DefaultExecutorService(cache);
List<Future<R>> futures = distributedExecutor.submitEverywhere(callable);
{code}
However, that doesn't work on a local cache (obviously). My proposal is to offer a
single way to process all entries in a cache, regardless of the cache mode or how the
cache is configured. (Perhaps I need to reword the request.)
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
2:39 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic commented on ISPN-2192:
-------------------------------------------
Ok I see what you mean Randall! You basically want to execute certain code on all cache
entries regardless of cache mode. We could make another class that implements
DistributedExecutorService, say DefaultLocalExecutorService?
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
2:58 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Randall Hauch commented on ISPN-2192:
-------------------------------------
Well, ideally I could execute code like this on any cache:
{code:java}
Cache<K, V> cache = ...
CacheCallable<K,V,R> callable = ...
CacheExecutorService executor = cache.getExecutor(); // or perhaps from a utility or
factory,
// but something that Infinispan
provides
List<Future<R>> futures = executor.submitEverywhere(callable);
{code}
Of course, I could still use my own {{CacheExecutorService}} if I knew which one would
work best.
I'm not sure this is terribly different than using {{DistributedCallable}} and
{{DistributedExecutorService}}, since those interfaces actually don't have anything
specific to being "distributed" other than their names (which is why I
originally suggested simply reusing them as-is). Perhaps if {{Cache*}} interfaces will be
created, the {{Distributed*}} interfaces could extend the newer {{Cache*}} interfaces.
WDYT?
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
3:06 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Randall Hauch edited comment on ISPN-2192 at 8/21/12 9:04 AM:
--------------------------------------------------------------
Yes, I originally suggested keeping/using the {{Distributed*}} interfaces because they
actually work semantically for all modes - the only thing "distributed" about
each of them is simply the name. The "submitEverywhere(...)" is generic enough
that I think that'd make sense even in a local cache.
However, it may make more sense in the long run to define new interfaces that are named
independently of the mode. For example:
{code:java}
Cache<K, V> cache = ...
CacheCallable<K,V,R> callable = ...
CacheExecutorService executor = cache.getExecutor();
List<Future<R>> futures = executor.submitEverywhere(callable);
{code}
Notice how Infinispan should IMO provide a way to obtain a proper {{CacheExecutorService}}
implementation based upon the configuration. The example above obtains it from the cache
(which IMO would be ideal), though I can see a factory or utility class being useful here.
Of course, I could still use my own {{CacheExecutorService}} if I knew which one would
work best.
Really, this is not very different than using {{DistributedCallable}} and
{{DistributedExecutorService}} - just the names have changed slightly. Whether this is
important is up to the Infinispan team.
BTW, I think that the contract should be that the calling code always has to be prepared
to handle multiple Future<R> instances and be able to combine multiple {{R}}
results. Even though a naive local executor might only return one, an advanced local
executor implementation could parallelize the work and return multiple.
was (Author: rhauch):
Well, ideally I could execute code like this on any cache:
{code:java}
Cache<K, V> cache = ...
CacheCallable<K,V,R> callable = ...
CacheExecutorService executor = cache.getExecutor(); // or perhaps from a utility or
factory,
// but something that Infinispan
provides
List<Future<R>> futures = executor.submitEverywhere(callable);
{code}
Of course, I could still use my own {{CacheExecutorService}} if I knew which one would
work best.
I'm not sure this is terribly different than using {{DistributedCallable}} and
{{DistributedExecutorService}}, since those interfaces actually don't have anything
specific to being "distributed" other than their names (which is why I
originally suggested simply reusing them as-is). Perhaps if {{Cache*}} interfaces will be
created, the {{Distributed*}} interfaces could extend the newer {{Cache*}} interfaces.
WDYT?
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
12:54 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic updated ISPN-2192:
--------------------------------------
Component/s: Distributed Execution and Map/Reduce
Forum Reference: https://community.jboss.org/message/588864#588864 (was:
https://community.jboss.org/message/588864#588864)
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
6:38 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2192:
--------------------------------
Labels: modshape (was: )
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
Labels: modshape
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
2:03 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2192:
--------------------------------
Fix Version/s: 5.2.0.CR1
5.2.0.Final
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Manik Surtani
Priority: Critical
Labels: modshape
Fix For: 5.2.0.CR1, 5.2.0.Final
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
7:54 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic reassigned ISPN-2192:
-----------------------------------------
Assignee: Vladimir Blagojevic (was: Manik Surtani)
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Vladimir Blagojevic
Priority: Critical
Labels: modshape
Fix For: 5.2.0.CR1, 5.2.0.Final
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
10 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic updated ISPN-2192:
--------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1497
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Vladimir Blagojevic
Priority: Critical
Labels: modshape
Fix For: 5.2.0.CR1, 5.2.0.Final
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
12:29 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2192:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.2.0.Beta6
(was: 5.2.0.CR1)
Resolution: Done
Integrated.
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Vladimir Blagojevic
Priority: Critical
Labels: modshape
Fix For: 5.2.0.Final, 5.2.0.Beta6
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
12:29 p.m.
[
https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2192:
-------------------------------
Status: Pull Request Sent (was: Open)
Allow using Distributed Execution against any cache (not just
clustered caches)
-------------------------------------------------------------------------------
Key: ISPN-2192
URL: https://issues.jboss.org/browse/ISPN-2192
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.1.2.FINAL
Reporter: Randall Hauch
Assignee: Vladimir Blagojevic
Priority: Critical
Labels: modshape
Fix For: 5.2.0.Final, 5.2.0.Beta6
It is often desirable to process all entries in a cache, and there is no reliable and
consistent way to do that for any cache.
If a cache is clustered, then map-reduce can be used (although IIUC it currently
doesn't guarantee to process non-materialized entries for caches that have a cache
store) and distributed execution can be used (IIUC this will be called for all keys owned
by the cluster node). However, neither of these work on local caches.
If a cache is local and there is no cache store, then apparently {{keySet()}} does work
and allows a client to iterate over the keys in the local cache. However, if the local
cache is configured to have a cache store, then the {{keySet()}} method will return only
the keys for the materialized entries and does not return all of the keys in the cache. Of
course, if a local cache does have a cache store, then its possible to obtain the keys
using {{CacheLoader.loadAllKeys(...)}} (obviously this is probably not something a client
should do).
In short, it should be possible to use Distributed Execution against any cache,
regardless of its configuration. (Ideally, it would be possible for Map-Reduce to also be
used against any cache.)
--
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
4161
days inactive
4277
days old
infinispan-issues@lists.jboss.org
13 comments
5 participants
participants (5)
-
Dan Berindei (JIRA) -
Mircea Markus (JIRA)
-
Randall Hauch (JIRA)
-
SBS JIRA Integration (JIRA)
-
Vladimir Blagojevic (JIRA)