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

ASF GitHub Bot commented on TWILL-138:
--------------------------------------

Github user chtyim commented on a diff in the pull request:

    https://github.com/apache/twill/pull/14#discussion_r83471254
  
    --- Diff: twill-api/src/main/java/org/apache/twill/api/ResourceReport.java 
---
    @@ -61,4 +63,11 @@
        * @return list of services of the application master.
        */
       List<String> getServices();
    +
    +  /**
    +   * Get the map of the log levels enabled for the twill application.
    +   *
    +   * @return the map of the log level arguments of the twill application
    +   */
    +  Map<String, Map<String, LogEntry.Level>> getLogLevels();
    --- End diff --
    
    Why have this method? The log levels are already contained inside 
individual `TwillRunResources`.


> Runtime change of Application runnable log level
> ------------------------------------------------
>
>                 Key: TWILL-138
>                 URL: https://issues.apache.org/jira/browse/TWILL-138
>             Project: Apache Twill
>          Issue Type: New Feature
>          Components: core
>            Reporter: Henry Saputra
>
> With TWILL-24 is supported for setting log level when starting the Twill 
> application, next enhancement is to able to send command to update the 
> aggregate log level for a particular runnable in a Twill application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to