[
https://issues.apache.org/jira/browse/TWILL-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664846#comment-15664846
]
ASF GitHub Bot commented on TWILL-138:
--------------------------------------
Github user yaojiefeng commented on a diff in the pull request:
https://github.com/apache/twill/pull/14#discussion_r87879825
--- Diff:
twill-api/src/main/java/org/apache/twill/internal/DefaultTwillRunResources.java
---
@@ -90,8 +104,14 @@ public Integer getDebugPort() {
}
@Override
+ @Deprecated
public Level getLogLevel() {
- return logLevel;
+ return getLogLevels().get(Logger.ROOT_LOGGER_NAME);
--- End diff --
This will return `null` if the `ContainerLiveNodeData` not getting created
or updated. We want it to be like that since it will reflect the actual state
of the container, right?
> 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)
