[
https://issues.apache.org/jira/browse/HBASE-12922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292100#comment-14292100
]
Hadoop QA commented on HBASE-12922:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12694559/HBASE-12922.1.patch
against master branch at commit 1c1a306b2e4bdd5a4ff877634c5064097637e2f2.
ATTACHMENT ID: 12694559
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+"NoSQL" is a general term meaning that the database isn't an RDBMS which
supports SQL as its primary access language, but there are many types of NoSQL
databases: BerkeleyDB is an example of a local NoSQL database, whereas HBase is
very much a distributed database.
+Technically speaking, HBase is really more a "Data Store" than "Data Base"
because it lacks many of the features you find in an RDBMS, such as typed
columns, secondary indexes, triggers, and advanced query languages, etc.
+* Automatic sharding: HBase tables are distributed on the cluster via regions,
and regions are automatically split and re-distributed as your data grows.
+* MapReduce: HBase supports massively parallelized processing via MapReduce
for using HBase as both source and sink.
+* Block Cache and Bloom Filters: HBase supports a Block Cache and Bloom
Filters for high volume query optimization.
+* Operational Management: HBase provides build-in web-pages for operational
insight as well as JMX metrics.
+If you only have a few thousand/million rows, then using a traditional RDBMS
might be a better choice due to the fact that all of your data might wind up on
a single node (or two) and the rest of the cluster may be sitting idle.
+Even HDFS doesn't do well with anything less than 5 DataNodes (due to things
such as HDFS block replication which has a default of 3), plus a NameNode.
+HBase can run quite well stand-alone on a laptop - but this should be
considered a development configuration only.
+See the <<datamodel>> and the rest of this chapter for more information on how
HBase achieves its goals.
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/12586//console
This message is automatically generated.
> Post-asciidoc conversion fix-ups part 2
> ---------------------------------------
>
> Key: HBASE-12922
> URL: https://issues.apache.org/jira/browse/HBASE-12922
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Lars Francke
> Assignee: Lars Francke
> Attachments: HBASE-12922.1.patch
>
>
> I did read through large parts of the documentation and fixed what I found.
> Some of it is AsciiDoc stuff, some is contents, some is grammar, some typos
> fixed etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
