hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1789) [hbaseshell] output formatting
Date Thu, 27 Sep 2007 23:11:52 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530869
] 

Hadoop QA commented on HADOOP-1789:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12366627/consoletable-3.patch
against trunk revision r580166.

    @author -1.  The patch appears to contain 1 @author tags which the Hadoop community has
agreed to not allow in code contributions.

    javadoc -1.  The javadoc tool appears to have generated  messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/835/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/835/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/835/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/835/console

This message is automatically generated.

> [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
>             Fix For: 0.15.0
>
>         Attachments: console_templates.patch, consoletable-2.patch, consoletable-3.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.


Mime
View raw message