I think we do eventually want to support it. For highly selective queries the existing dictionary and min/max filtering can already be very effective. In addition, we plan to add indexes for finer-grained page pruning. See https://issues.apache.org/jira/browse/IMPALA-5842
After all those improvements, it's not clear what the additional benefit of later materialization is going to be in practice. Do you have a case in mind that specifically requires late materialization to work well? On Tue, Mar 20, 2018 at 12:47 AM, Antoni Ivanov <[email protected]> wrote: > Hi, > > > > You can ignore my question, Found the relevant JIRA - > https://issues.apache.org/jira/browse/IMPALA-2017 So I guess the answer > is not yet. > > > > Regards, > > Antoni > > > > *From:* Antoni Ivanov > *Sent:* Tuesday, March 20, 2018 9:45 AM > *To:* '[email protected]' <[email protected]> > *Subject:* Does Impala supports or plan to support Late Materialization > > > > I don’t mean partition pruning but as described in > > https://aws.amazon.com/about-aws/whats-new/2017/12/amazon- > redshift-introduces-late-materialization-for-faster-query-processing/ > > > > It basically pre-fetches first the filter columns and then after applying > the filter it fetches only the data from the rest of columns only if filter > applies. > > > > Thanks >
