[
https://issues.jboss.org/browse/ISPN-4021?page=com.atlassian.jira.plugin....
]
Vladimir Blagojevic edited comment on ISPN-4021 at 2/25/14 2:25 PM:
--------------------------------------------------------------------
Dan, we have two options here:
a) we can pass intermediate cache directly to MapReduceTask and thus force correct typing
b) pass the cache name only
Option b) gives more flexibility in the future if things change internally while option a)
minimizes potential errors on the behalf of user at the expense of flexibility b) has.
What should we do?
was (Author: vblagojevic):
Dan, we have two options here:
a) we can pass intermediate cache directly to MapReduceTask and thus force correct typing
b) pass the cache name only
Option b) gives more flexibility in the future if things change internally while option a)
minimizes potential errors on the behalf of user at the expense of flexibility a) has.
What should we do?
Allow each Map/Reduce task to use a different cache configuration
-----------------------------------------------------------------
Key: ISPN-4021
URL:
https://issues.jboss.org/browse/ISPN-4021
Project: Infinispan
Issue Type: Feature Request
Components: Core, Distributed Execution and Map/Reduce
Affects Versions: 6.0.1.Final
Reporter: Dan Berindei
Assignee: Vladimir Blagojevic
Fix For: 7.0.0.Final
Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should
be able to use its own cache configuration.
--
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