hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8016) HBase as an embeddable library, but still using HDFS
Date Thu, 07 Mar 2013 02:08:14 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595437#comment-13595437
] 

Andrew Purtell commented on HBASE-8016:
---------------------------------------

On this:

bq. An application using this library would gain all of the advantages of HBase without adding
any additional administrative complexity of managing HBase as a distributed service.

I'm skeptical. Since HBase is by definition a distributed datastore, and gains most (if not
just about all) of its advantages from being a distributed service, I don't see how one does
not use "LevelHBase" to gain all the advantages of HBase without building a distributed service
which incorporates it. How does this avoid "additional administrative complexity?" At which
point you have a new datastore which might by chance incorporate some HBase code. TANSTAAFL
                
> HBase as an embeddable library, but still using HDFS
> ----------------------------------------------------
>
>                 Key: HBASE-8016
>                 URL: https://issues.apache.org/jira/browse/HBASE-8016
>             Project: HBase
>          Issue Type: Wish
>            Reporter: eric baldeschwieler
>
> This goes in the "strange idea" bucket...  
> I'm looking for a tool to allow folks to store key-value data into HDFS so that hadoop
companion layers & apps don't need to rely either on external database or a NoSQL store.
 HBase itself is often not running on such clusters and we can not add it as a requirement
for many of the use cases I'm considering.
> But...  what if we produced a library that provided the basic HBase API (creating tables
& putting / getting values...) and this library was pointed at HDFS for durability.  This
library would effectively embed a region server and the the master in a node and provide only
API level access within that JVM.  We would skip marshaling & networking, gaining a fair
amount of efficiency.  An application using this library would gain all of the advantages
of HBase without adding any additional administrative complexity of managing HBase as a distributed
service.
> Thoughts?
> Example use cases...  Right now a typical hadoop install runs serval services that use
databases (Oozie, HCat, Hive ...).  What if some of these could be ported to use HDFS itself
as their store with the HBase API provided to manage their data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message