Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
The patch about aggregating tablet statistics on the kudu-master is on the way. And I think it's important to expose these statistics in client api by which the query engine can optimize their query plan. For example: (1) adjust the order of scanning tables, (2) Split a big tablet into multiple range pieces(KUDU-2437) to improve concurrency automatically, (3) speed up the query like "select count( *) from table".