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

Posted to dev@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2022/02/13 04:27:00 UTC

[jira] [Resolved] (YUNIKORN-1073) AllocationAskRelease field allocationkey should be allocationKey

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

Weiwei Yang resolved YUNIKORN-1073.
-----------------------------------
    Fix Version/s: 1.0.0
       Resolution: Fixed

> AllocationAskRelease field allocationkey should be allocationKey
> ----------------------------------------------------------------
>
>                 Key: YUNIKORN-1073
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1073
>             Project: Apache YuniKorn
>          Issue Type: Task
>          Components: core - common, scheduler-interface, shim - kubernetes
>            Reporter: Wilfred Spiegelenburg
>            Assignee: ted
>            Priority: Major
>              Labels: newbie, pull-request-available
>             Fix For: 1.0.0
>
>
> The case for the allocationkey in the AllocationAskRelease is incorrect and should be fixed. Proper capitalisation would be allocationKey as it is used in all other places in the interface.
> This has a flow on effect from the interface to the core and shim as the field name in the message changes. It is a simple change that can almost be done by a search and replace and 2 times a go.mod file updates
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org