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

genericqa commented on HADOOP-11640:
------------------------------------

| (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  5s{color} 
| {color:red} HADOOP-11640 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-11640 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12701791/HADOOP-11640.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/14311/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> add user defined delimiter support to Configuration
> ---------------------------------------------------
>
>                 Key: HADOOP-11640
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11640
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Xiaoshuang LU
>            Assignee: Xiaoshuang LU
>            Priority: Major
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-11640.patch
>
>
> As mentioned by org.apache.hadoop.conf.Configuration.getStrings ("Get the 
> comma delimited values of the name property as an array of Strings"), only 
> comma separated strings can be used.  It would be much better if user defined 
> separators are supported.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to