You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/11/04 18:44:00 UTC
[jira] [Commented] (YUNIKORN-2925) Remove internal objects from application REST response
[ https://issues.apache.org/jira/browse/YUNIKORN-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895394#comment-17895394 ]
Craig Condit commented on YUNIKORN-2925:
----------------------------------------
Historical information has no place in the REST API at all. That's what the event system is for.
> Remove internal objects from application REST response
> ------------------------------------------------------
>
> Key: YUNIKORN-2925
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2925
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - common
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Major
> Labels: release-notes
>
> The REST api for application objects exposes an internal object type (resource) directly without conversion. That means any internal representation change will break REST compatibility. This should never have happened and needs to be reversed ASAP. All other REST calls
> The other problem with the exposed information is that it is only accurate for the COMPLETING or COMPLETED state of an application. The data is incomplete at any other state as it is only updated when an allocation finishes. Running allocations are not included.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org