geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-7075) "class" field should not be part of json results
Date Wed, 11 Sep 2019 18:51:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927897#comment-16927897
] 

ASF subversion and git services commented on GEODE-7075:
--------------------------------------------------------

Commit 3cbbd27ba0af8130f4a783045ff116d86722c154 in geode's branch refs/heads/develop from
Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3cbbd27 ]

GEODE-7075: 'class' field should not be part of json results (#4011)



> "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
>          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)

Mime
View raw message