You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Krystal (JIRA)" <ji...@apache.org> on 2017/03/31 21:34:42 UTC

[jira] [Updated] (DRILL-4974) NPE in FindPartitionConditions.analyzeCall() for 'holistic' expressions

     [ https://issues.apache.org/jira/browse/DRILL-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krystal updated DRILL-4974:
---------------------------
    Reviewer: Krystal  (was: Chun Chang)

> NPE in FindPartitionConditions.analyzeCall() for 'holistic' expressions
> -----------------------------------------------------------------------
>
>                 Key: DRILL-4974
>                 URL: https://issues.apache.org/jira/browse/DRILL-4974
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>    Affects Versions: 1.6.0, 1.7.0, 1.8.0
>            Reporter: Karthikeyan Manivannan
>            Assignee: Karthikeyan Manivannan
>             Fix For: 1.9.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The following query can cause an NPE in FindPartitionConditions.analyzeCall() if the fileSize column is a partitioned column. 
> SELECT  fileSize FROM dfs.`/drill-data/data/` WHERE compoundId LIKE 'FOO-1234567%'
> This is because, the LIKE is treated as a holistic expression in FindPartitionConditions.analyzeCall(), causing opStack to be empty, thus causing opStack.peek() to return a NULL value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)