Skip to main content

How to Filter Multiple Columns in HBase Using SingleColumnValueFilter

By Anonymous
Filtering multiple columns in HBase requires combining several SingleColumnValueFilter instances inside a FilterList. By enforcing boolean AND logic across column families, only rows where all required columns contain valid values are returned. This pattern helps control scan output precisely even in older HBase deployments.

HBase is a column-oriented database, storing data by column family and qualifier. When executing a scan, filters help reduce the returned data set to only rows matching specific criteria.

A frequent challenge is filtering on more than one column simultaneously. For example, you may require that two or more specific columns must contain valid values before a row qualifies.

The practical solution is to use multiple SingleColumnValueFilter objects combined in a FilterList. This gives you boolean AND logic across all defined filters. 


List<Filter> list = new ArrayList<Filter>(2);

// Filter on family "fam1", qualifier "VALUE1"
Filter filter1 = new SingleColumnValueFilter(
    Bytes.toBytes("fam1"),
    Bytes.toBytes("VALUE1"),
    CompareOp.DOES_NOT_EQUAL,
    Bytes.toBytes("DOESNOTEXIST")
);
filter1.setFilterIfMissing(true);
list.add(filter1);

// Filter on family "fam2", qualifier "VALUE2"
Filter filter2 = new SingleColumnValueFilter(
    Bytes.toBytes("fam2"),
    Bytes.toBytes("VALUE2"),
    CompareOp.DOES_NOT_EQUAL,
    Bytes.toBytes("DOESNOTEXIST")
);
filter2.setFilterIfMissing(true);
list.add(filter2);

FilterList filterList = new FilterList(list);

Scan scan = new Scan();
scan.setFilter(filterList);

Each SingleColumnValueFilter tests for the presence and validity of a single column. Using CompareOp.DOES_NOT_EQUAL with a placeholder value such as DOESNOTEXIST is a common way to ensure a column must contain meaningful data.

The call setFilterIfMissing(true) ensures that rows without the column are automatically excluded. When wrapped inside a FilterList, these filters collectively enforce that all conditions must be satisfied before the row is returned.

You can add as many filters as required. This pattern is still widely used for precise data selection in legacy HBase clusters.

Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Building a Model-Agnostic Multi-Agent System with OpenClaw

By
Over one week we rebuilt our AI stack around OpenClaw’s multi-agent architecture to avoid provider lock-in and stop wasting premium tokens. By aligning models to tasks, diversifying fallbacks across providers, enforcing minimal tool access, and switching to memory-first workflows with ephemeral sessions, we reduced token usage per task by about 70% and cut our monthly bill by 77% while improving operational resilience. How We Achieved 77% Cost Reduction and Provider Independence Over the past week, we rebuilt our AI infrastructure around OpenClaw’s multi-agent architecture. The result was a 77% cost reduction , provider independence , and a delegation system that routes work to the most cost-effective model for each job. Below is the technical journey of optimizing a 7-agent squad with OpenClaw. The Challenge: Model Provider Lock-In We started with a simple problem: our entire squad defaulted to a single model provider. This created three issues: Cost inefficiency beca...
Read more

Why Is Customer Obsession Disappearing?

By
Many companies trade real customer-obsession for automated, low-empathy support. Through examples from Coinbase, PayPal, GO Telecommunications and AT&T, this article shows how reliance on AI chatbots, outsourced call centers, and KPI-driven workflows erodes trust, NPS and customer retention. It argues that human-centric support—treating support as strategic investment instead of cost—is still a core growth engine in competitive markets. It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers. The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and no...
Read more

What are the performance implications of cross-platform execution within Wayang?

By
Apache Wayang ® enables cross-platform execution across multiple data processing platforms such as Spark, Flink, Java Streams, PostgreSQL or GraphChi. This capability fundamentally changes the performance behavior of distributed data pipelines. Wayang reduces manual data movement by selecting where each operator should run, but crossing platform boundaries still introduces serialization cost, shifts in locality, different memory strategies and new tuning constraints. Understanding these dynamics is essential before adopting Wayang for multi-platform pipelines at scale. Apache Wayang is a cross-platform data processing framework that lets developers run a single logical pipeline across engines such as Apache Spark, Apache Flink or a native Java backend. It provides an abstraction layer and a cost-based optimizer that selects the execution platform for each operator. This flexibility introduces new performance variables that do not exist in single-engine systems. Engine boundaries ...
Read more