[
https://issues.apache.org/jira/browse/DRILL-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467858#comment-17467858
]
ASF GitHub Bot commented on DRILL-8088:
---------------------------------------
jnturton commented on pull request #2412:
URL: https://github.com/apache/drill/pull/2412#issuecomment-1003948739
> i'm sure you have already discussed this, but i would like to know why we
are not migrating to arrow and cannot find any information about this decision.
As far as i know, arrow was inspired by drill and on the arrow homepage they
have still the picture with drill on it but drill does not use arrow.
https://arrow.apache.org/overview/
> Is there any official statement from the project for the arrow
support/migration?
@Z0ltrix there isn't an official statement that I know of. It's too big a
question for a comment thread answer and a good topic for a community meetup
with some senior devs present. I believe that to some extent Drill's vector
engine has developed in its own direction since Arrow arrived and the best
route forward for Drill is now not entirely obvious, and needs some thought.
Significant pros for Arrow are that it is maintained externally and I believe
its performance is very good.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Improve expression evaluation performance
> -----------------------------------------
>
> Key: DRILL-8088
> URL: https://issues.apache.org/jira/browse/DRILL-8088
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Codegen
> Reporter: wtf
> Assignee: wtf
> Priority: Minor
>
> Found unnecessary map copy when doing expression evaluation, it will slow
> down the codegen when the query include many "case when" or avg/stddev(the
> reduced expressions include "case when"). In our case, the query include 314
> avg, it takes 3+ seconds to generate the projector expressions(Intel(R)
> Xeon(R) CPU E5-2682 v4 @ 2.50GHz 32cores).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
