geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-393) FunctionContext should provide a Cache
Date Thu, 29 Jun 2017 21:21:00 GMT


ASF subversion and git services commented on GEODE-393:

Commit d82a548f6575e7d691c83bc0558aca981689d601 in geode's branch refs/heads/develop from
[;h=d82a548 ]

GEODE-393: Providing cache for FunctionContext

Added the ability to pass a Cache to a function context as well as tests to check for this.

This closes #589
This closes #74

> FunctionContext should provide a Cache
> --------------------------------------
>                 Key: GEODE-393
>                 URL:
>             Project: Geode
>          Issue Type: Improvement
>          Components: functions
>            Reporter: Dan Smith
>            Assignee: David Anuta
>              Labels: starter
> FunctionContext has methods to get the arguments to the function and the result sender,
but there is no way to get the Cache or DistributedSystem.
> This means pretty much any function will need to statically look up the cache using CacheFactory.getAnyInstance().
While that works, it makes it impossible to write unit tests for functions by passing in a
mock cache.
> Note that onRegion functions are provided a RegionFunctionContext, which does provide
these functions with a means to look up the cache, but not all functions are applied to a

This message was sent by Atlassian JIRA

View raw message