Performance of cloud bigtable row filtering

Question

What is happening on the bigtable server when you issue a prefix scan with row filtering?

Say you perform a prefix scan using filtering and as time goes on, more rows end up getting filtered out. I'm wondering if performance becomes degraded due to filtering.

Is Cloud Bigtable efficient at doing prefix scans that need to filter out lots of rows?

Answer 1

Is Cloud Bigtable efficient at doing prefix scans that need to filter out lots of rows?

In short no, it is not efficient. To make your query more efficient, you can promote the field(s) you are using in the query: move it(them) from the column data into the row key.