[
https://issues.apache.org/jira/browse/HADOOP-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Izaak Rubin updated HADOOP-1789:
--------------------------------
Attachment: console_templates.patch
This patch changes the way that console tables are printed; instead of a
hard-coded fixed-size ascii table, the patch brings in FreeMarker templates to
make an ascii table of arbitrary width.
At present the changes in this patch are functional, but only preliminary.
There are only templates for printing ascii tables, although with the given
setup it would be easy to add xml and html templates. The FreeMarker jar,
which is required for this patch to work, is not included. For more on
FreeMarker and where to get this jar, see:
http://freemarker.org/
All tests passed on my local machine. However, note that TestConsoleTable
(added in this patch) may not always work because it depends on a relative path
for finding the FreeMarker templates directory. The functionality thus depends
on what directory the test is run from (at present there are template
directories in HADOOP_HOME and HBASE_HOME). As I said, this is only
preliminary -- ultimately these files will be added to the classpath and there
won't be a dependency on a relative path. The primary purpose of this patch is
only to demonstrate the capabilities and advantages of using FreeMarker
templates as opposed to hard-coded output formatting.
> [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
> Priority: Minor
> Attachments: console_templates.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.
