# Install hbase with Homebrew, Nix Hadoop database: a distributed, scalable, big data store. Version 2.6.6 via Homebrew; verified 2026-06-22. ## Install ```sh sudo av install brew:hbase ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install hbase ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#hbase ``` Evidence: nixpkgs package indexes: hbase from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Package facts - **Package key:** brew:hbase - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.6.6 - **Source summary:** Hadoop database: a distributed, scalable, big data store - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 AND GPL-3.0-or-later - **Source archive:** - **Last updated:** 2026-06-22T14:03:42-07:00 - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - hbase (cli) - start-hbase.sh (cli) - stop-hbase.sh (cli) - hbase (alias) - start-hbase.sh (alias) - stop-hbase.sh (alias) ## Dependencies - lzo - openjdk@17 ## Build dependencies - ant ## Install behavior - Post-install hook: not defined - Service: declared - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.6.6 - Package-manager updated: 2026-06-22 - Local data: ok - Upstream repository: https://hbase.apache.org - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage Apache HBase is a distributed, scalable, Bigtable-like data store built on Hadoop and HDFS for random, real-time read/write access to very large sparse tables. In package-manager terms it is a heavyweight data-system package: a CLI, daemons, configuration directory, Java/Hadoop dependency stack, and operational database all in one. ### Project history The official reference guide's history appendix begins with Google's 2006 Bigtable paper, then places the start of HBase development at the end of 2006. The project was designed to bring Bigtable-like capabilities to the Hadoop ecosystem rather than to be a standalone relational database. HBase became a Hadoop sub-project in 2008 and an Apache top-level project in 2010. That transition matters historically because it moved HBase from an add-on in the Hadoop orbit to an Apache project with its own project management committee, release process, community, and operational identity. The HBase website describes the system as a distributed, scalable big-data store for random, real-time read/write access. It emphasizes billions of rows, millions of columns, consistent operations, automatic failover and sharding on Hadoop/HDFS, and APIs including Java, REST, Thrift, filters, and Bloom filters. The reference guide is unusually central to the project history: it covers standalone quick starts, distributed modes, configuration files, shell usage, schema design, MapReduce integration, security, architecture, backup/restore, replication, APIs, performance tuning, operations, and development. That breadth reflects HBase's evolution from a storage engine into a production database system with a large operator surface. ### Adoption history The official Powered by Apache HBase page lists user-submitted deployments across companies, institutions, and projects. It includes early production or large-scale use cases from Adobe, Facebook Messages, Flurry, HubSpot, OCLC WorldCat, OpenLogic, Trend Micro, Twitter, WorldLingo, Yahoo, and others. The adoption examples show why HBase became important in the Hadoop era: teams needed low-latency reads and updates, wide sparse rows, time-series or event data, search and analytics backends, and MapReduce/Spark-adjacent processing without abandoning the commodity-cluster model. HBase's adoption was also ecosystem-driven. Its value came not only from the database itself, but from living near HDFS, Hadoop MapReduce, ZooKeeper, Java clients, REST/Thrift gateways, and later higher-level systems such as Trafodion or Spark integrations. ### How it is used The quick start uses a standalone instance where the Master, RegionServer, and ZooKeeper daemon run in one JVM, then connects through the hbase shell to create, list, describe, put, and scan a table. Production usage moves the same model into distributed deployments with separate daemons and HDFS storage. Administrators configure HBase through files such as conf/hbase-site.xml and conf/hbase-env.sh, start and stop services with scripts such as start-hbase.sh and stop-hbase.sh, and use the shell, Java API, REST, Thrift, MapReduce jobs, and operational tools to manage data and clusters. ### Why package nerds care HBase is a classic package-manager stress test because installing the package is only the beginning. The formula has to deliver shell commands and scripts, but the real system depends on Java compatibility, Hadoop/HDFS behavior, ZooKeeper coordination, configuration files, daemon management, and careful version matching. For package nerds, HBase also represents the Hadoop-era pattern where a local package can be used for development or a single-node quick start, while production meaning lives in clusters, configuration, and service orchestration. That makes its package metadata deceptively small compared with its operational footprint. ### Timeline - 2006: Google publishes the Bigtable paper. - 2006: HBase development starts near the end of the year. - 2008: HBase becomes a Hadoop sub-project. - 2010: HBase becomes an Apache top-level project. - 2020s: The official site continues to present HBase as a top-level Apache project and Bigtable-like Hadoop database. ### Related projects - Google Bigtable is the direct design reference named by the HBase documentation. - Apache Hadoop, HDFS, ZooKeeper, MapReduce, Spark, REST, Thrift, and Apache Trafodion are related technologies in the official documentation and adoption pages. - HBase's source repository is managed by Apache through Git/GitBox. ### Sources - - - - ## Security Notes broad file, network, media, or database tool signal. formula declares a Homebrew service. - **Geiger risk:** orange / medium - broad file, network, media, or database tool signal - formula declares a Homebrew service ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: conf/hbase-site.xml, conf/hbase-env.sh ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** hbase - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Nix - hbase: normalized package name match | nixpkgs package indexes: hbase from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix ## Related links - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [openjdk@17](https://www.automicvault.com/pkg/brew/openjdk-17/) - Runtime dependency declared by Homebrew. - [ant](https://www.automicvault.com/pkg/brew/ant/) - Build dependency declared by Homebrew. - [opentsdb](https://www.automicvault.com/pkg/brew/opentsdb/) - Popular package that depends on this formula. - [neo4j](https://www.automicvault.com/pkg/brew/neo4j/) - Shares av.db curated category or tags: cli, data, database, databases, java. - [cassandra](https://www.automicvault.com/pkg/brew/cassandra/) - Shares av.db curated category or tags: cli, data, database, databases, distributed-database. - [h2](https://www.automicvault.com/pkg/brew/h2/) - Shares av.db curated category or tags: cli, data, database, databases, java. - [ssdb](https://www.automicvault.com/pkg/brew/ssdb/) - Shares av.db curated category or tags: cli, data, database, databases, nosql. - [apache-geode](https://www.automicvault.com/pkg/brew/apache-geode/) - Shares av.db curated category or tags: cli, data, database, databases. - [cdb](https://www.automicvault.com/pkg/brew/cdb/) - Shares av.db curated category or tags: cli, data, database, databases. - [check_postgres](https://www.automicvault.com/pkg/brew/check-postgres/) - Shares av.db curated category or tags: cli, data, database, databases. - [cql](https://www.automicvault.com/pkg/brew/cql/) - Shares av.db curated category or tags: cli, data, database, databases. - [hadoop](https://www.automicvault.com/pkg/brew/hadoop/) - Local package facts share a topical domain. Shared terms: big, big-data, cli, data, distributed. ## Combined YAML source View the package source record on GitHub. [combined/hbase.yml](https://github.com/automic-vault/db/blob/main/combined/hbase.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph