Hbase

(39)
4.2 out of 5 stars

A scalable, distributed database that supports structured data storage for large tables. Use HBase when you need random, realtime read/write access to Big Data.

Work for Hbase?

Learning about Hbase?

We can help you find the solution that fits you best.

Hbase Reviews

Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • User Industry
Ratings
Company Size
User Role
User Industry
Showing 43 Hbase reviews
LinkedIn Connections
Hbase review by <span>Prabhudayal A.</span>
Prabhudayal A.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Big Data NoSQL database

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product

Surely, but for NoSQL database

What business problems are you solving with the product? What benefits have you realized?

We are storing data from csv into Hbase after making an HFile .. Java implementation of map reduce is done for the same.

Sign in to G2 Crowd to see what your connections have to say about Hbase
Headshots
Hbase review by <span>Roshan M.</span>
Roshan M.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Big Data No SQL Storage

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product

For storing bulk datain a tabular manner, I would recommend Hadoop Hbase, but for small amount of data, I personally would not suggest the use of this tool.

What business problems are you solving with the product? What benefits have you realized?

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.

What Key-Value Stores solution do you use?

Thanks for letting us know!
Hbase review by <span>Prashanth P.</span>
Prashanth P.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Hadoop NoSQL Database

What do you like best?

Hadoop Hbase is a fault tolerance No SQL data base, 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.

What do you dislike?

The major drawback of Hbase is that is 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.

Recommendations to others considering the product

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

What business problems are you solving with the product? What benefits have you realized?

We are using Hbase to store all the data from old file system i.e., traditional file system to Hadoop.

As we are aware that data is growing day by day, so 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.

Hbase review by <span>Sushant D.</span>
Sushant D.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

Big Data - NoSQL DB

What do you like best?

Hbase is a noSQL database which can handle, large amount of data easily.

It is also fault tolerance.

The schema of Hbase is also very flexible and at any point of time we can add new columns to the table. Only column families need to be defined initially.

What do you dislike?

As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data.

In Hbase joins are not supported, we need to connect it ti either hive to do so.

Recommendations to others considering the product

To store, huge volume of data, and if no transaction support is required, then I'd surely recommend this component of Hadoop.

What business problems are you solving with the product? What benefits have you realized?

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.

Hbase review by <span>Saugandh K.</span>
Saugandh K.
Validated Reviewer
Verified Current User
Invitation from G2 Crowd
Reviewed On

A good new NoSQL: HBase

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product

Highly recommend if dealing with bulk and variety of data as no schema is required during DDL.

What business problems are you solving with the product? What benefits have you realized?

In our business we are using it to store data and metadata of the complete Content Management System of our client.

Hbase review by <span>Rupesh A.</span>
Rupesh A.
Validated Reviewer
Invitation from G2 Crowd
Reviewed On

NO Sql database

What do you like best?

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 hortanworks. So, it is a very good product to handle big data solution.

What do you dislike?

the way data is printed on console is not so user friendly. So we had to use some abstraction over hbase (eg apache phoenix) so there is one new component to handle.

Recommendations to others considering the product

Hbase can be helpful for few scenarios where you need a lot of data in db and also u want it to be accessed easily on basis of similarity of data. Like personal information are stored close by.

What business problems are you solving with the product? What benefits have you realized?

We are using it to store email files directly by bulkloading 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 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.

Kate avatar
Kate from G2 Crowd

Learning about Hbase?

I can help.
* We monitor all Hbase reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.