Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
We do lots of matching on columns. We have different kinds of matchers dependent on how the scanner was configured. Down in HAS, we have a map of family name to its matchers. There is no need of the Map since column matching is done at the family/store context only. Removing should save on some unnecessary CPU (I saw up to 10% in simple seek+scan test – so hopefully this comes down to 5 or 4%).