drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-1680) Use a different expession for ArraySegment and NamedSegment accessors
Date Tue, 11 Nov 2014 06:37:33 GMT

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

Jacques Nadeau commented on DRILL-1680:

You can tell the difference between the two by looking at the data type of the operand.  If
integer, then Array.  If char type, NamedSegment.  Doesn't this solve your issue?

> 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
> 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

View raw message