apache/hbase

Apache HBase

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 12th, 2026
Created on May 23rd, 2014
Open Issues & Pull Requests: 393 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 3,398
Total Stargazers: 5,558 (+0)
Total Subscribers: 377 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Apache HBase is a distributed, column-oriented database that provides Bigtable-like capabilities on top of Apache Hadoop. It stores data in a versioned, distributed manner designed for structured data at scale, modeling its architecture after Google's Bigtable paper and leveraging Hadoop's distributed storage layer.

HBase solves the problem of storing and accessing large volumes of structured data across distributed clusters. It organizes data into column families rather than traditional rows, allowing efficient storage and retrieval of sparse datasets. The system handles versioning natively, maintaining multiple timestamped versions of cell values, which enables time-travel queries and recovery scenarios. Its distributed architecture spreads data across many nodes, providing horizontal scalability and fault tolerance through replication.

HBase suits projects requiring low-latency random read and write access to massive datasets, particularly those with sparse or semi-structured data patterns. It works well in analytical pipelines built on Hadoop ecosystems and for applications needing strong consistency with automatic failover. Teams should adopt it when they need to scale beyond what traditional relational databases can handle and when their access patterns favor key-based lookups over complex joins. The tool is less suitable for applications requiring complex transactions across multiple rows or those with primarily sequential scan workloads where simpler solutions would suffice.

The project maintains active development across multiple areas. Contributions flow through a formal Apache process requiring account requests processed manually by maintainers. The team engages with users through dedicated mailing lists for announcements and discussions, alongside real-time communication via a dedicated Slack channel. The project hosts comprehensive documentation including a reference guide and quick-start materials on its website, reflecting ongoing investment in helping new users understand and deploy the system.