drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kunal Khatua (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (DRILL-6211) Optimizations for SelectionVectorRemover
Date Thu, 08 Mar 2018 23:56:00 GMT

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

Kunal Khatua reassigned DRILL-6211:

    Assignee: salim achouche

> Optimizations for SelectionVectorRemover 
> -----------------------------------------
>                 Key: DRILL-6211
>                 URL: https://issues.apache.org/jira/browse/DRILL-6211
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Codegen
>            Reporter: Kunal Khatua
>            Assignee: salim achouche
>            Priority: Major
>             Fix For: 1.14.0
> Currently, when a SelectionVectorRemover receives a record batch from an upstream operator
(like a Filter), it immediately starts copying over records into a new outgoing batch.
> It can be worthwhile if the RecordBatch can be enriched with some additional summary
statistics about the attached SelectionVector, such as 
> # number of records that need to be removed/copied
> # total number of records in the record-batch
> The benefit of this would be that in extreme cases, if *all* the records in a batch need
to be either truncated or copies, the SelectionVectorRemover can simply drop the record-batch
or simply forward it to the next downstream operator.

This message was sent by Atlassian JIRA

View raw message