You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Aman Sinha (JIRA)" <ji...@apache.org> on 2014/02/07 20:17:26 UTC

[jira] [Created] (DRILL-361) Optimization for aggregation functions workspace

Aman Sinha created DRILL-361:
--------------------------------

             Summary: Optimization for aggregation functions workspace 
                 Key: DRILL-361
                 URL: https://issues.apache.org/jira/browse/DRILL-361
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Aman Sinha


Currently, when an aggregation operator populates its outgoing record batch, it goes through the value vectors in its workspace and produces the output value.. for instance if the aggregate was AVG,  the aggregate function workspace variables are sum and count, and we compute the sum/count to populate the output record.   However, this is sub-optimal for the case where the aggregate function is simply doing a SUM or COUNT etc.  In those cases, we should be able to directly transfer the entire workspace value vector to the outgoing batch and get better performance.    We could maintain some property in the aggregate function itself that indicates whether it is a candidate for such an operation. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)