[
https://issues.apache.org/jira/browse/GEODE-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933707#comment-15933707
]
ASF subversion and git services commented on GEODE-2634:
--------------------------------------------------------
Commit d61bb33832446b7621c45d4ec86e797f3a7f68ce in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d61bb33 ]
GEODE-2634: use log4j levels for auto-completion
* change the auto complete to use log4j levels.
* be able to handle both log4j levels and logwriter levels in the commands
* add validation of log level whenever possible for these commands
* Move the conversion between the two to a LogLevel class and add unit tests
> gfsh export logs command should be able to filter logs on log-level
> -------------------------------------------------------------------
>
> Key: GEODE-2634
> URL: https://issues.apache.org/jira/browse/GEODE-2634
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
> Reporter: Swapnil Bawaskar
>
> If I try to filter the exported logs by a log level, I get the following
> exceptions:
> {noformat}
> gfsh>export logs --dir=tmp --log-level=config
> Invalid log level: config
> gfsh>export logs --dir=tmp --log-level=config
> Invalid log level: config
> gfsh>export logs --dir=tmp --log-level=warning
> Invalid log level: warning
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
