[jira] [Assigned] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks

2018-01-22 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-3554:


Assignee: Anilkumar Gingade  (was: Kirk Lund)

> Document not invoking CacheFactory.getAnyInstance() from user callbacks
> ---
>
> Key: GEODE-3554
> URL: https://issues.apache.org/jira/browse/GEODE-3554
> Project: Geode
>  Issue Type: New Feature
>  Components: core
>Reporter: Fred Krone
>Assignee: Anilkumar Gingade
>Priority: Major
>  Labels: cache, geode-150, pull-request-available
>
> As long as the product continues to invoke user plug-in callbacks during 
> startup (and with the main thread), we probably need to document a warning 
> not to use CacheFactory.getAnyInstance() as the API call is common in 
> plug-ins and this will freeze startup.
> We are planning on deprecating and removing CacheFactory.getAnyInstance() 
> anyway.
> Documentation should recommend using preferred APIs:
> * FunctionContext.getCache()
> * Event.getRegion().getCache()
> We could expose Event.getCache() to make it more obvious to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (GEODE-3554) Document not invoking CacheFactory.getAnyInstance() from user callbacks

2018-01-22 Thread Kirk Lund (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund reassigned GEODE-3554:


Assignee: Kirk Lund

> Document not invoking CacheFactory.getAnyInstance() from user callbacks
> ---
>
> Key: GEODE-3554
> URL: https://issues.apache.org/jira/browse/GEODE-3554
> Project: Geode
>  Issue Type: New Feature
>  Components: core
>Reporter: Fred Krone
>Assignee: Kirk Lund
>Priority: Major
>  Labels: cache, geode-150, pull-request-available
>
> As long as the product continues to invoke user plug-in callbacks during 
> startup (and with the main thread), we probably need to document a warning 
> not to use CacheFactory.getAnyInstance() as the API call is common in 
> plug-ins and this will freeze startup.
> We are planning on deprecating and removing CacheFactory.getAnyInstance() 
> anyway.
> Documentation should recommend using preferred APIs:
> * FunctionContext.getCache()
> * Event.getRegion().getCache()
> We could expose Event.getCache() to make it more obvious to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)