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

Chris Nauroth commented on HADOOP-13556:
----------------------------------------

[~lmccay], if I remember correctly, that won't be sufficient to re-trigger 
pre-commit, because it is aware that the timestamp hasn't changed on the 
attachment.  I think it works if you attach a new file with the same contents.  
However, an even easier option for committers is to login to Jenkins and submit 
it manually.

https://builds.apache.org/job/PreCommit-HADOOP-Build/

Login with your standard Apache credentials.  Then, click Build with 
Parameters.  Then, enter the JIRA ID (just the number, not the "HADOOP-" 
prefix.)  I just submitted one for you here:

https://builds.apache.org/job/PreCommit-HADOOP-Build/10426/

I think as a committer you have all the necessary rights to do this yourself 
too.  There are different jobs for each JIRA project (PreCommit-HDFS-Build, 
PreCommit-YARN-Build, etc.), so it needs to be submitted under the job that 
matches the JIRA project ID.

> Change Configuration.getPropsWithPrefix to use getProps instead of iterator
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-13556
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13556
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>             Fix For: 2.8.0, 3.0.0-alpha1
>
>         Attachments: HADOOP-13556-001.patch, HADOOP-13556-002.patch
>
>
> Current implementation of getPropsWithPrefix uses the 
> Configuration.iterator() method. This method is not threadsafe.
> This patch will reimplement the gathering of properties that begin with a 
> prefix by using the safe getProps() method.



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

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

Reply via email to