[
https://issues.apache.org/jira/browse/HADOOP-11967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946195#comment-15946195
]
Hadoop QA commented on HADOOP-11967:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 8s{color}
| {color:red} HADOOP-11967 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-11967 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12747505/HADOOP-11967.003.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/11979/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Prefix of configuration properties given to "hadoop trace" command should be
> omittable
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-11967
> URL: https://issues.apache.org/jira/browse/HADOOP-11967
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tracing
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Priority: Minor
> Attachments: HADOOP-11967.001.patch, HADOOP-11967.002.patch,
> HADOOP-11967.002.patch, HADOOP-11967.003.patch
>
>
> Configuration properties for tracing must be properly prefixed based on
> context in configuration files such as core-site.xml or hdfs-site.xml. When
> users run {{hadoop trace}} command, the context and prefix is obvious from
> the target server host and could be omittable to reduce typing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
