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

Hemanth Yamijala commented on HADOOP-5721:
------------------------------------------

I don't think the failure is related to this patch at all and shouldn't hold 
commit of this patch.

I committed a change to capacity scheduler (HADOOP-5726) which changed the 
capacity scheduler config template file (capacity-scheduler.xml.template). At 
build time, in a clean workspace, the template file is copied to become the 
capacity-scheduler.xml file. But this does not happen if the file already 
exists (as it could in an existing workspace). In such a case, the new code is 
looking for some config properties that changed in HADOOP-5726, which are not 
found in the older capacity-scheduler.xml file and hence fails. 

I don't know how this can be fixed without changing the logic by which the 
build script copies the template files to the actual files. Any ideas, Nigel ?

> Provide EditLogFileInputStream and EditLogFileOutputStream as independent 
> classes 
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-5721
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5721
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.19.1
>            Reporter: Luca Telloli
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5721.patch, HADOOP-5721.patch, HADOOP-5721.patch, 
> HADOOP-5721.patch, HADOOP-5721.patch, HADOOP-5721.patch, HADOOP-5721.patch, 
> HADOOP-5721.patch, HADOOP-5721.patch
>
>
> EditLogFileInputStream and EditLogFileOutputStream are currently part of 
> FSEditLog. With this patch we want to extract them and provide as independent 
> classes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to