In #30744, we added an optimization for point lookups so that they would only scan as many column families as necessary rather than the entire row. This speeds up scans and reduces contention.
However, we're currently only getting this benefit in tablereader. We should apply the same optimization to other processors which do fetches: indexJoiner, joinReader (lookup joins), and zigzagJoiner. Ideally we can find an approach which doesn't add redundant code to all three places.
In #30744, we added an optimization for point lookups so that they would only scan as many column families as necessary rather than the entire row. This speeds up scans and reduces contention.
However, we're currently only getting this benefit in tablereader. We should apply the same optimization to other processors which do fetches: indexJoiner, joinReader (lookup joins), and zigzagJoiner. Ideally we can find an approach which doesn't add redundant code to all three places.