[
https://issues.apache.org/jira/browse/PHOENIX-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461293#comment-15461293
]
Andrew Purtell commented on PHOENIX-3218:
-----------------------------------------
bq. HBase is a KV store
This is commonly stated, but isn't quite right. It is more accurate to say
HBase implements the BigTable data model, described in
http://static.googleusercontent.com/media/research.google.com/en//archive/bigtable-osdi06.pdf
. You can stop there, but as to what I mean: "KV store" describes a flat
keyspace with single key for lookup and does not imply a partitioning scheme.
In contrast, HBase (and BigTable) presents multiple keyspaces (aka tables) and
is a distributed ordered tree.
> First draft of Phoenix Tuning Guide
> -----------------------------------
>
> Key: PHOENIX-3218
> URL: https://issues.apache.org/jira/browse/PHOENIX-3218
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Peter Conrad
> Attachments: Phoenix-Tuning-Guide.md
>
>
> Here's a first draft of a Tuning Guide for Phoenix performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)