You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Gang Yan (JIRA)" <ji...@apache.org> on 2019/08/12 17:22:00 UTC

[jira] [Created] (GEODE-7076) Pdx should not have group, groups, and uri

Gang Yan created GEODE-7076:
-------------------------------

             Summary: Pdx should not have group, groups, and uri
                 Key: GEODE-7076
                 URL: https://issues.apache.org/jira/browse/GEODE-7076
             Project: Geode
          Issue Type: Improvement
          Components: management
            Reporter: Gang Yan


For REST API V2 for management, Swagger shows that the model for Pdx includes "group", "groups" and "uri".
None of these should be specified when doing a POST Pdx. If you do specify group you get an error saying Pdx is only at the cluster level.
uri also does not add any value on a POST, and if we do add support for GET to Pdx, it really isn't needed either since they had to do a GET on the uri itself so we don't need to tell them what the uri is.
The uri comes from: org.apache.geode.management.api.RestfulEndpoint.getUri(). Could the Pdx class override this and mark it with @JsonIgnore?
group and groups comes from CacheElement. Could the Pdx class override them and mark them with @JsonIgnore?

The java-api exposes these on Pdx and it would be best if it didn't. If we did some refactoring so that Pdx did not have these methods on it them this would clean up the rest-api automatically.

Objective:
 # find a way to hide these attributes from Swagger docs.
 # is there a way to hide "group"/"groups" from the java api as well



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)