That somewhat depends on what you mean by something else. For MapR-DB, the only difference is lack of support for co-processors. That means that switching from HBase is pretty easy.
For a non-HBase key-value store that is not HBase API compatible, you will have a much bigger job ahead of you. In particular, Kylin depends critically on having efficient range scans which is a rare design point for kv stores. That means you probably won't be able to get usable performance from any system that doesn't support efficient key-order range scans. What KV store are you thinking of using? On Thu, Jul 23, 2015 at 6:07 PM, Stephen Boesch <[email protected]> wrote: > I am inquiring if anyone has had any thoughts on this - and also where is > the documentation on how to plugin a different key-value storage engine > than HBase? > > thanks! > > > 2015-07-12 17:08 GMT-07:00 Stephen Boesch <[email protected]>: > > > > > HBase/Zookeeper is a heavy/complex stack when considering small-scale > > development and testing . The Mini HBase cluster is tricky to configure > > and consumes a fair amount of memory. Zookeeper suffers from timeout > > issues that complicate debugging cycles. Region server management also > > complicates testing It may be preferable to have an option to avoid > these > > considerations altogether when working on/developing portions of logic > that > > do not interface directly with the indexing and metadata logic. > > > > In the eBay blog there is a single sentence mentioning it "may" be > > possible to use a different K-V backend than HBase: > > > > http://www.ebaytech > > blog.com/2014/10/20/announcing-kylin-extreme-olap-engine-for-big-data/ > > > > > > > > - *Storage Engine: *This engine manages the underlying storage – > > specifically the cuboids, which are stored as key-value pairs. The > Storage > > Engine uses HBase ... *Kylin can also be extended to support other K-V > > systems, such as Redis <http://redis.io/>.* > > > > Is there any documentation on how that extension may be achieved? A > > pluggable interface? I would for example like to see Cassandra as a > > drop-in replacement for HBase. > > > > Thanks > > > > stephenb > > >
