You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/05/22 22:07:02 UTC

[jira] [Commented] (AURORA-461) Modify API return types and values to allow client logging.

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

Bill Farner commented on AURORA-461:
------------------------------------

{quote}
The client can select which messages get shown to the user based on their severity/type tags.
{quote}

If it's okay with you, i'd like to hold off on this tagging.  However, i'll design the structs to leave the door open to this.  We can discuss further in review, though.

> Modify API return types and values to allow client logging.
> -----------------------------------------------------------
>
>                 Key: AURORA-461
>                 URL: https://issues.apache.org/jira/browse/AURORA-461
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Mark Chu-Carroll
>            Assignee: Bill Farner
>
> Modify the return type/values from the scheduler API calls so that:
> (1) They no longer return irrelevant messages in the message field.
>   (ie, don't explain the fact that you succeeded; you've already got
>   an OK resultCode to tell you that)
> (2) Modify the return type messages field, so that instead of being a single string, it's a list of structs, each of which has a string message field, and some sort of type field that works like the severity on a logging pair. The client can select which messages get shown to the user based on their severity/type tags.



--
This message was sent by Atlassian JIRA
(v6.2#6252)