[
https://issues.apache.org/jira/browse/HADOOP-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated HADOOP-5467:
--------------------------------
Attachment: HADOOP-5467.patch
Updated patch based on Nicholas' review. Thanks.
* There is no longer a default filename. -o is a required cli argument. You're
correct that it was confusing.
* Re-wrote the help section
* Clarified why Ls overrides -skipBlocks
* Mentioned that no cluster is need to run oiv
* Corrected cli argument typos
* Removed all references to FSImage, replaced with just Image. The tool is in
hdfs package, therefore it is redundant to refer to fs again.
* Changed XML to Xml in class name.
Test patch was +1, all unit tests pass on my local machine.
> Create an offline fsimage image viewer
> --------------------------------------
>
> Key: HADOOP-5467
> URL: https://issues.apache.org/jira/browse/HADOOP-5467
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Attachments: fsimage.xml, fsimageV18, fsimageV19, HADOOP-5467.patch,
> HADOOP-5467.patch, HADOOP-5467.patch, HADOOP-5467.patch, HADOOP-5467.patch,
> HADOOP-5467.patch
>
>
> It would be useful to have a tool to examine/dump the contents of the fsimage
> file to human-readable form. This would allow analysis of the namespace
> (file usage, block sizes, etc) without impacting the operation of the
> namenode. XML would be reasonable output format, as it can be easily viewed,
> compressed and manipulated via either XSLT or XQuery.
> I've started work on this and will have an initial version soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
