Hi all,
In our kudu source code, we just cull row-sets when lower_bound_key and exclusive_upper_bound_key are existing at the same time. And if not, we will grab all row-sets of the tablet, then have to seek the key in ‘CFileSet::Iterator::PushdownRangeScanPredicate’ for the unnecessary row-sets (which will waste disk io). I am curious about that is it possible and helpful to support half open-ended range or equality value while culling row-sets? Thanks in advance. 何李夫 2017-04-10 16:06:24
