You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/11 18:39:00 UTC

[jira] [Resolved] (HBASE-8016) HBase as an embeddable library, but still using HDFS

     [ https://issues.apache.org/jira/browse/HBASE-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-8016.
----------------------------------------
    Resolution: Won't Fix

> 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
>            Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.7#820007)