On Mon, Feb 24, 2014 at 10:55 PM, Vladimir Blagojevic
vblag...@redhat.comwrote:
See inline
On 2/24/2014, 12:57 PM, Mircea Markus wrote:
On Feb 19, 2014, at 8:45 PM, Vladimir Blagojevic vblag...@redhat.com
wrote:
Hey guys,
As some of you might know we have received additional
On 2/25/2014, 7:33 AM, Dan Berindei wrote:
Do we really need special support for distributed tasks to write
results to another cache? We already allow a task to do
cache.getCacheManager().getCache(outputCache).put(k, v)
Yeah, very good point Dan. Thanks for being sanity check. Mircea?
On Feb 25, 2014, at 3:09 PM, Vladimir Blagojevic vblag...@redhat.com wrote:
On 2/25/2014, 7:33 AM, Dan Berindei wrote:
Do we really need special support for distributed tasks to write results to
another cache? We already allow a task to do
Hey,
I am starting to like this thread more and more :-) In conclusion, for
distributed executors we are not adding any new APIs because Callable
implementers can already write to cache using existing API. We don't
have to add any new elaborate callback/listener API either as users have
not
On Tue, Feb 25, 2014 at 9:31 PM, Vladimir Blagojevic vblag...@redhat.comwrote:
Hey,
I am starting to like this thread more and more :-) In conclusion, for
distributed executors we are not adding any new APIs because Callable
implementers can already write to cache using existing API. We
On Feb 19, 2014, at 8:45 PM, Vladimir Blagojevic vblag...@redhat.com wrote:
Hey guys,
As some of you might know we have received additional requirements from
community and internally to add a few things to dist.executors and
map/reduce API. On distributed executors front we need to
See inline
On 2/24/2014, 12:57 PM, Mircea Markus wrote:
On Feb 19, 2014, at 8:45 PM, Vladimir Blagojevic vblag...@redhat.com wrote:
Hey guys,
As some of you might know we have received additional requirements from
community and internally to add a few things to dist.executors and
map/reduce
Hey guys,
As some of you might know we have received additional requirements from
community and internally to add a few things to dist.executors and
map/reduce API. On distributed executors front we need to enable
distributed executors to store results into cache directly rather than
