Kunal Khatua created DRILL-6211:
-----------------------------------
Summary: 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
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
(v7.6.3#76005)
