[
https://issues.apache.org/jira/browse/HADOOP-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-1789:
--------------------------
Attachment: factory.patch
Adds a factory for table formatters that commands such as select go via
emitting header, row, and footer. Currently only an ascii table formatter
provided. It removes the index column (mysql doesn't do this). Still needs to
read configurations -- either from hbase-site or from command-line and system
properties -- and in general, the approach is still not satisfing. Needs more
consideration.
As said above, it would be useful if the columns had type information. This
could be passed to the formatter so it could use the right type when it does
its toString before emitting cell content.
Columns will never have type 'size' info as they do in sql databases making it
hard to vary the column width appropriately as is done in mysql. In hbase,
column size has to be fixed (for ascii table output)
Currently we output row, column, and cell columns. We should also allow for
output of timestamp.
mysql has --html, --xml, and tab separation of columns when you run with
--silent. You can also ask to suppress headers.
> [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, 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.
