You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 16:02:00 UTC

[jira] [Updated] (KUDU-3033) Add min/max values for the non-primary key columns in the metadata of rowsets/datablocks

     [ https://issues.apache.org/jira/browse/KUDU-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke updated KUDU-3033:
------------------------------
    Component/s: perf

> Add min/max values for the non-primary key columns in the metadata of rowsets/datablocks
> ----------------------------------------------------------------------------------------
>
>                 Key: KUDU-3033
>                 URL: https://issues.apache.org/jira/browse/KUDU-3033
>             Project: Kudu
>          Issue Type: New Feature
>          Components: cfile, perf, tablet
>            Reporter: LiFu He
>            Priority: Major
>
> It's possible to add min/max values for the non-primary key columns in the metadata of diskrowset/datablock, and then we can skip decoding/evaluating the unnecessary diskrowset/datablock while scanning. Just like the "compute stats" feature on impala, and the only difference is that kudu supports updates. So, the min/max values should be invalid if the columns that have deltas while scanning.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)