Hbase is used as a distributed wide-column database for storing and retrieving large datasets, especially where teams need fast access to data by key. Its use is often tied to Hadoop-based data processing.

What company sizes and industries is Hbase the best fit for?

Hbase is most often a fit for larger organizations, with positive users also represented in mid-market and small businesses. The industries with the strongest presence include:

Company size — Enterprise: The most prominent segment among positive users.
Company size — Mid-market: Also well represented.
Company size — Small business: Present among positive users as well.
Industry — Information technology and computer software: A recurring setting for Hbase use.
Industry — Banking and financial services: Commonly represented, often for large-scale data storage and processing.
Industry — Telecommunications: Another recurring use context.

How long does it take to implement Hbase across a team?

Implementation timelines vary, but 1–3 months is the most commonly reported time to go live. Other reported timelines span from less than a day to more than a year.

Time to go live	Relative frequency
1–3 months	Most common
Less than 1 month	Also reported
3–6 months	Also reported
More than 12 months	Less common
6–12 months	Less common
Less than 1 day	Less common

What customer support options does Hbase provide, and how do users find the overall support experience?

Hbase is an open-source project with community-oriented support; users value community knowledge and online resources, though support experiences can be uneven. Community help is useful for finding answers, while troubleshooting and resolving complex issues can take effort.

What is the experience like for teams switching to Hbase from another tool?

Teams have moved to Hbase when existing relational or other data stores could not handle their data volume, scaling needs, or performance requirements. The transition can bring faster access to large datasets and a closer fit with Hadoop-based workloads, but it also means adapting to a nonrelational model and a less familiar query approach. Prior systems include relational databases such as MySQL and PostgreSQL, as well as other NoSQL and data platforms.

What tools and platforms does Hbase integrate with, and how do these integrations help users get more value from the product?

Hbase is used with Hadoop ecosystem components and connected to query, analytics, and application layers. These connections let teams work with large datasets in their existing data pipelines and serve queried data to applications.

Hadoop and data processing: Hadoop, HDFS, MapReduce, and Spark.
Query and search: Hive, Apache Phoenix, Apache Solr, and Elasticsearch.
Application and data access: Java clients, REST APIs, and Kafka.
Reporting and visualization: Tableau and Banana.

What features or capabilities could make Hbase even more useful?

Hbase could be more approachable for teams that need to query, manage, and tune it. Recurring improvement areas include:

Querying: Provide a more intuitive, SQL-like query experience for common data operations.
Indexing and data access: Make it easier to index and query beyond the row key.
Cross-table operations: Add more direct support for joins and related relational-style operations.
Administration: Simplify setup, configuration, monitoring, and performance tuning.
Developer experience: Make the APIs, tools, and management interface easier to use.

G2 reviews are authentic and verified.

Here's how.

Gubendran L.

Senior Java J2EE BigData Consultant @ Petra Systems Inc

Computer Software

Mid-Market (51-1000 emp.)

Originally submitted 6/9/2015

"Very good NoSQL DB"

4/5

What do you like best about Hbase?

The best with Hbase is data stored in hadoop cluster. The read is much faster. Data is replicated in clusters. Region Transition upon server failures is faster. Version based storage as defined. RDBMS (MySQL) we use need to maintain version data like history. Defining FamilyName helps grouping set of qualifiers (Columns) in a given row is good to fetch only certain group of columns data. Filters (RowFilter, SingleColumnFilter API) is flexible to fetch data based on requirement by filtering pattern. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

SQL like Query language missing in hbase. Like Hive we need Query support. Binary data based storage. Every time in code we need to encrypt / decrypt data into Binary format and store it in DB. Lot of code we need to write.Update record is missing. So, we need to delete and put every-time or we may fetch rowId, version, timestamp to override the value in update. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

When you evaluate NoSQL for your organization / product, its worth to evaluate HBase for your requirements. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

We are storing huge amount of reporting data from energy utilities and other utilities data into Hbase on a daily / hourly basis and we have Map/Reduce framework to do analyse data from Hbase. We felt Hbase is perfect to work with Hadoop Map/Reduce framework. Reading data from Hbase was really faster and we could read huge data from reporting table where we couldn't read from MySQL. Replication, Scalability, Performance overall for NoSQL Hbase is good. Review collected by and hosted on G2.com.

tousif k.

Senior Software Engineer

Computer Software

Enterprise (> 1000 emp.)

Originally submitted 1/10/2016

"excellent bigdata storage"

5/5

What do you like best about Hbase?

nosql architecture, ease of scaling up to several nodes and easy retrieval of information, best suited for unstructured data. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

very complex software and requires monitoring for performance Review collected by and hosted on G2.com.

Rupesh A.

system engineer

Information Technology and Services

Enterprise (> 1000 emp.)

9/8/2017

"NO Sql database"

4/5

What do you like best about Hbase?

Best thing is we can store large amount of data in it and related data are stored closely so that can be retrieved quickly. Column family helps me to segregate similar data. So, they can be extracted fastly. It has a very good support from community of Hortonworks. So, it is a very good product to handle big data solution. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

The way data is printed on console is not so user friendly. So we had to use some abstraction over HBase (e.g., Apache Phoenix) so there is one new component to handle. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

HBase can be helpful for few scenarios where you need a lot of data in DB and also you want it to be accessed easily on basis of similarity of data. Like personal information are stored close by. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

We are using it to store email files directly by bulk loading and then retrieving it using Apache Phoenix. Apache HBase helps us to store data by making HFiles and directly uploading those HFiles to region servers. Instead of having a large number of tables in HBase, we are creating a single table for all email types and then in Phoenix we are making views on top of that table and firing queries by Phoenix. Review collected by and hosted on G2.com.

Roshan M.

System Engineer

Information Technology and Services

Enterprise (> 1000 emp.)

6/23/2017

"Big Data No SQL Storage"

4.5/5

What do you like best about Hbase?

Hbase can easily manage, bulk amount of data in an efficient and robust manner. It is considered to be a powerful NoSQL tool, which helps in data management, and provides an ease in fast retrieval and manipulation of the same. It is better than traditional file system, because of the efficiency, which it provides for the same amount of system, and major advantage is the use of commodity hardware, to store the data. Also it is fault tolerant, as it keeps replica of the data stored, so in case of failure, the replica can be used. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

Hbase is not recommended for small amount of data, as it will take, some time in processing, making it not very efficient for that. It has a single point of failure, i.e., HMaster, so if H Master fails, Hbase goes down, and we will not be able to perform any operations, until problem is resolved. We cannot easily perform joins on Hbase, making it a complex tool to perform basic operations. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

For storing bulk data in a tabular manner, I would recommend Hadoop Hbase, but for small amount of data, I personally would not suggest the use of this tool. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

We are moving from traditional file system to Hadoop file system, and to store the data in a tabular manner, we are using Hbase. As the data is increasing day by day, the need to manage the same is also required, which is incorporated by Hadoop. Review collected by and hosted on G2.com.

Nikhila D.

System Engineer

Information Technology and Services

Enterprise (> 1000 emp.)

9/6/2017

"Store huge amount of data with ease"

4.5/5

What do you like best about Hbase?

1) Creating a table with any number of column family names, or any number of columns is easy

2) Map Reduce program helps in loading bulk amount of data in a very short span of time

3) The way we can view the tables and querying the table is very easy as its a NOSQL database

4)It has its own scheduler i.e OOZIE scheduler which is built on yarn user.

5) Kerborization is one big advantage which is supported by HBASE. This ensures the data is secure

6)To maintain the data integrity of data the checksum is used to check corrupted data. This API of HBASE is very helpful Review collected by and hosted on G2.com.

What do you dislike about Hbase?

1) The only way to identify the individual records is through the row key, there is no other alternative

2) As it is a NOSQL, joins is not supported when we query for multiple tables Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

Yes definitely Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

1) To store the data related to banking services

2) Emails, chats, fax data between customers and the bank are stored in HBASE under different tables

3) The investor profile details, are stored in HBASE

4) The jobs are scheduled using the OOZIE scheduler by cron expressions

5)Used to update the mutation records as well Review collected by and hosted on G2.com.

swetha m.

Senior System Engineer

Information Technology and Services

Enterprise (> 1000 emp.)

9/4/2017

"Data Encyclopedia"

4/5

What do you like best about Hbase?

1) Speed- Hbase helps in running map reduce programs which can load petabytes of data to Hbase in parallel which speeds our work. 2) NoSQL Database- As Hbase is a noSQL database, we can store data in terms of key-value pairs in a list of column families, this helps in querying faster and can have multiple values in a column. 3) Storage- Hbase can store both metadata as well as content which reduces multiple resources in use. 4) Oozie Scheduler- Hbase has its own built-in Oozie scheduler which can schedule jobs using specified cron expression, Oozie has its own UI where you can see the status of the job and refer to logs as well in case of failures which is very helpful. 5) Hadoop ecosystem also has a distributed file system which partitions data among different data nodes which helps in storing huge files. I have used it to store HFiles in HDFS and finally load them to Hbase using a map reduce program in Java. 6) Phoenix which supports SQL on Hbase, We are using this to query Hbase which speeds up the scan of tables. 7) We are also using checksum to check whether the data entered the base is corrupted or not which helps in tracking and reconciliation of data. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

1) As Hbase is a noSQL database, querying with joins is not possible. 2) When we map Phoenix with Hbase table, we are unable to create a column other than in Hbase and update it, only vice versa is possible. 3) The restriction of Oozie scheduler which can be run only by yarn users and can pick files only from HDFS. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

1) Hbase- NoSQL database which helps in storage of big data and even helps in querying. 2) Supports parallel programming using map reduce which fastens our work. 3) Phoenix runs SQL on Hbase which scans faster. 4) Has built-in scheduler-oozie. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

1) Hbase has helped in loading petabytes of data using map reduce programs in Java. We were able to load metadata as well as content to Hbase. 2) We are able to apply retention policy on records by scanning multiple tables using Phoenix. 3) We have used Kerberization to enhance the security of our modules in the Hadoop ecosystem as well. Review collected by and hosted on G2.com.

Prashanth P.

System Engineer

Information Technology and Services

Enterprise (> 1000 emp.)

6/19/2017

"Hadoop NoSQL Database"

4/5

What do you like best about Hbase?

Hadoop Hbase is a fault tolerance No SQL database, which can be used for analysis. It makes replica of the data which is loaded, which makes it more reliable. It has out of box features like, auto-sharding and auto-failover. It can be integrated with Hadoop Hive, which is also a component of Hadoop, to use SQL like queries. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

The major drawback of Hbase is that it does not have transaction support. We cannot perform joins in Hbase easily, to perform joins we have to either write complex map-reduce code, or integrate with Hadoop Hive. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

To store a bulk amount of data, I would suggest Hbase. But if the amount of data to be stored is less, then it is not recommended. Also, if we do not require transaction support with a huge amount of data, then we can always go for Hbase. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

We are using Hbase to store all the data from the old file system, i.e., traditional file system, to Hadoop. As we are aware that data is growing day by day, we need better products to store and manage this data, which is easily achievable by Hbase. So we are moving all our data into Hadoop storage in a tabular form in Hbase tables. Review collected by and hosted on G2.com.

prabhudayal a.

Senior Software Engineering

Information Technology and Services

Enterprise (> 1000 emp.)

Originally submitted 6/2/2017

"Big Data NoSQL database"

4/5

What do you like best about Hbase?

1. The capacity, storage and processing of bulk data, in such a robust manner. 2. Flexible schema as we can add n numbers of attributes in a column family at run time without declaring them at the time of table creation. 3. Fault tolerance- As we know mapReduce runs internally for all kind of operation, In case of failure scenarios mapper and reducer job handles it. 4. Versioning of records- Default feature for versioning is available. If that is enabled, hbase updates the record and also keeps the old record data. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

1. Transaction concept is not applicable.-as its a noSQL database 2. No other primary key can be defined other than the row key. 3-Indexing of row key is a feature by default- but we can not explicitly index any other value, as we can not have any primary key other than row key itself. Review collected by and hosted on G2.com.

Saugandh K.

Software Engineer

Enterprise (> 1000 emp.)

6/19/2017

"A good new NoSQL: HBase"

4/5

What do you like best about Hbase?

The robustness of the application in terms of capacity, storage and processing of bulk data is the best. Also not having a table schema helps a lot which allows us to have as many columns as possible on the go without defining them. The concept of versioning of the records helps us to compare data properly and also store both the data if required. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

Highly recommend if dealing with bulk and variety of data as no schema is required during DDL. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

In our business we are using it to store data and metadata of the complete Content Management System of our client. Review collected by and hosted on G2.com.

Sushant D.

System Engineer

Information Technology and Services

Enterprise (> 1000 emp.)

6/9/2017

"Big Data - NoSQL DB"

4/5

What do you like best about Hbase?

Hbase is a noSQL database which can handle large amounts of data easily. It is also fault-tolerant. The schema of Hbase is also very flexible and at any point in time, we can add new columns to the table. Only column families need to be defined initially. Review collected by and hosted on G2.com.

What do you dislike about Hbase?

As Hbase is a noSQL database, it doesn't have transaction support and we cannot perform many operations on the data. In Hbase, joins are not supported, and we need to connect it to Hive to do so. Review collected by and hosted on G2.com.

Recommendations to others considering Hbase:

To store a huge volume of data, and if no transaction support is required, then I'd surely recommend this component of Hadoop. Review collected by and hosted on G2.com.

What problems is Hbase solving and how is that benefiting you?

We are storing all the data after converting it to a CSV to Hbase, as the amount of data is increasing day by day, and the traditional storage system cannot suffice the need. Review collected by and hosted on G2.com.

Questions about Hbase? Ask real users or explore answers from the community

Get practical answers, real workflows, and honest pros and cons from the G2 community or share your insights.

Shashank Sah

•

Last activity over 6 years ago

In HBase, we cannot implement any cross data operations and joining operations, of course, we can implement the joining operations using MapReduce, which would take a lot of time to designing and development. How we can improve this??

1 Upvote

Join the conversation

Guest User

What do you recommend for organizations considering Hbase for their database management needs?

0 Upvotes

Join the conversation

View all Discussions