You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Owen Nichols (Jira)" <ji...@apache.org> on 2019/09/11 23:54:00 UTC

[jira] [Resolved] (GEODE-7075) "class" field should not be part of json results

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

Owen Nichols resolved GEODE-7075.
---------------------------------
    Fix Version/s: 1.11.0
       Resolution: Fixed

> "class" field should not be part of json results
> ------------------------------------------------
>
>                 Key: GEODE-7075
>                 URL: https://issues.apache.org/jira/browse/GEODE-7075
>             Project: Geode
>          Issue Type: Improvement
>          Components: management
>            Reporter: Gang Yan
>            Assignee: Darrel Schneider
>            Priority: Major
>             Fix For: 1.11.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
>  
> For REST API V2 for management, Most all of the rest api results that describe something end up having a "class" field with a value that shows the java class that implemented this json doc. This seems like an implementation detail that should be ignored when creating the json doc. For and example see MemberInformation and MemberConfig when you hit the "members" endpoint.
> *TODO*
>  # hide for REST CALL
>  # show it for JAVA call



--
This message was sent by Atlassian Jira
(v8.3.2#803003)