[ 
https://issues.apache.org/jira/browse/DRILL-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529144#comment-16529144
 ] 

ASF GitHub Bot commented on DRILL-6561:
---------------------------------------

sohami opened a new pull request #1356: DRILL-6561: Lateral excluding the 
columns from output container provided by projection push into rules
URL: https://github.com/apache/drill/pull/1356
 
 
   This PR is dependent upon DRILL-6545 and has 2 commits from it for 
compilation. Once that is merged in this PR has to be rebased on master and 
then checked-in.
   
   @parthchandra - Please review it.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Lateral excluding the columns from output container provided by projection 
> push into rules
> ------------------------------------------------------------------------------------------
>
>                 Key: DRILL-6561
>                 URL: https://issues.apache.org/jira/browse/DRILL-6561
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Relational Operators
>    Affects Versions: 1.14.0
>            Reporter: Sorabh Hamirwasia
>            Assignee: Sorabh Hamirwasia
>            Priority: Major
>             Fix For: 1.14.0
>
>
> With DRILL-6545, LateralPop will have information about list of columns to be 
> excluded from the Lateral output container. Mostly this is used to avoid 
> producing origin repeated column in Lateral output if it's not required from 
> the projection list. This is needed because in absence of it Lateral has to 
> copy the repeated column N number of times where N is the number of rows in 
> right incoming batch for each left incoming batch row. This copy was very 
> costly both from memory and latency perspective. Hence avoiding it is a must 
> for Lateral-Unnest case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to