You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/26 18:06:05 UTC
[jira] [Closed] (GEODE-6869) decouple ClusterManagementService
query and response types
[ https://issues.apache.org/jira/browse/GEODE-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dick Cavender closed GEODE-6869.
--------------------------------
> decouple ClusterManagementService query and response types
> ----------------------------------------------------------
>
> Key: GEODE-6869
> URL: https://issues.apache.org/jira/browse/GEODE-6869
> Project: Geode
> Issue Type: Improvement
> Components: management
> Reporter: Owen Nichols
> Assignee: Owen Nichols
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> currently CMS calls like `list(CacheElement)` return CacheElement (or sometimes RuntimeCacheElement which uses inheritance+copy constructor rather than composition to add additional stats alongside the static config info)
> this has been "ok" so far, since most CMS calls focus on CRUD operations on things in cache.xml which already extend CacheElement. However, it would be cleaner to decouple the return type from the filter class, and not require either one to extend CacheElement, to give us more flexibility to expose things via CMS that aren't strictly elements of cache.xml
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)