[
https://issues.apache.org/jira/browse/HDFS-13890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603929#comment-16603929
]
Xiao Chen commented on HDFS-13890:
----------------------------------
Thanks for your thoughts on this [~adam.antal].
bq. ... should rather use hdfs ls command.
This goes into the question of use cases. I think ls can do most of the things
oiv can do, and the core difference being oiv gives someone the ability to
analyze the image in an _offline_ fashion. Out of the several oiv processors, I
think XML is the most powerful one. Delimited maybe more friendly on
post-processing (e.g. grep / awk / perl / whatever), but as you noticed doesn't
support snapshots well.
One improvement maybe we can do is, to support loading the snapshot /
snapshotdiff sections of the image. I don't know if that is necessary, because
1) I'm not sure how many people care about snapshot enough and use delimited
oiv 2) I'm not sure out of people in #1, what portion can live with just the
XML processor.
Anyways, because the output won't be as layered as xml, so we need to make sure
the delimited output makes sense.
bq. ...a bit complicated...
I think the credit goes to hdfs snapshot itself - be it oiv or inside NN. :)
> Allow Delimited PB OIV tool to print out INodeReferences
> --------------------------------------------------------
>
> Key: HDFS-13890
> URL: https://issues.apache.org/jira/browse/HDFS-13890
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Minor
>
> HDFS-9721 added the possibility to process PB-based FSImages containing
> snapshots by simply ignoring them.
> Although the XML tool can provide information about the snapshots, the user
> may find helpful if this is shown within the Delimited output (in the
> Delimited format).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
