You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by GitBox <gi...@apache.org> on 2018/07/12 00:23:01 UTC

[GitHub] bitblender opened a new pull request #1375: DRILL-6594: Data batches for Project operator are not being split properly and exceed the maximum specified

bitblender opened a new pull request #1375: DRILL-6594: Data batches for Project operator are not being split properly and exceed the maximum specified
URL: https://github.com/apache/drill/pull/1375
 
 
   This change fixes the incorrect accounting in the case where a columns is being projected more than once.
   
   ProjectMemoryManager was recording input column names of varlen columns, instead of output column names of these columns. Since input names are unique, this caused columns to be counted only once irrespective of the number of times they were being projected.
   
   Eg. select some_varchar_column_a as some_varchar_column_b, some_varchar_column_a as some_varchar_column_c....
   
   In this case, if input column name is used, the outputColumnSizes map in ProjectMemoryManger will have only one entry i.e some_varchar_column_a. ProjectMemoryManger should instead record some_varchar_column_b and some_varchar_column_c.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services