[
https://issues.apache.org/jira/browse/HADOOP-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531238
]
Hudson commented on HADOOP-1789:
--------------------------------
Integrated in Hadoop-Nightly #254 (See
[http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/254/])
> [hbaseshell] output formatting
> ------------------------------
>
> Key: HADOOP-1789
> URL: https://issues.apache.org/jira/browse/HADOOP-1789
> Project: Hadoop
> Issue Type: New Feature
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Fix For: 0.15.0
>
> Attachments: console_templates.patch, consoletable-2.patch,
> consoletable-3.patch, consoletable-4.patch, factory.patch
>
>
> hbaseshell currently outputs results using an ascii table.
> This issue is about the hbaseshell offering a number of output formats beyond
> plain ascii table. It would be grand if output formatting was pluggable so
> folks could add new ones as they saw fit.
> Currently, there is a painful need for unadorned output so folks can do a
> 'select page:content from webrepository where
> row="http://apache.com/index.html";; and they get back the page content only.
> Other output formats might be: csv, xml, or (x)html
> Other related things to consider, but probably not as part of this issue, is
> that if we output xml, then we should probably have a sympathetic input
> parser for xml files (similar for csv). Let this issue just be about
> formatting (another issue can be done to add pluggable input parsers). Where
> the output lands should also be done in another issue: i.e. dependent on the
> command, output probably default to stdout but folks should be able to
> designate an output file (and target filesystem) as in
> hdfs://master.hdfsnode.com:8990/output/dump.txt or file:///tmp/dump.txt or
> s3://...., etc.
> This issue is an outgrowth of HADOOP-1720
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
