You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Hanifi Gunes (JIRA)" <ji...@apache.org> on 2014/11/14 19:58:34 UTC

[jira] [Comment Edited] (DRILL-1680) Use a different expession for ArraySegment and NamedSegment accessors

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

Hanifi Gunes edited comment on DRILL-1680 at 11/14/14 6:58 PM:
---------------------------------------------------------------

My understanding is that changing the operator name disables pushdown into sub-scans. Am I right? If so, do we really want to disable pushdown into subscans?


was (Author: hgunes):
My understanding is that changing the operator name disables pushdown into sub-scans. Am I right? If so, do we really disable pushdown into subscans?

> Use a different expession for ArraySegment and NamedSegment accessors
> ---------------------------------------------------------------------
>
>                 Key: DRILL-1680
>                 URL: https://issues.apache.org/jira/browse/DRILL-1680
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization
>            Reporter: Hanifi Gunes
>            Assignee: Aman Sinha
>
> Drill planner treats ArraySegment accessors the same way with NamedSegment accessors. This ambiguity causes planner to loop indefinitely when projection pushdown is enabled (see DRILL-1455). We need to distinctly name two operators that have been used to access array segments and named segments. Array segments should still use ITEM. However named segments should be accessed via some other name just like GETCOLUMN/GETFIELD.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)