Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 13 Dec 2012 17:36:12 +0000 (UTC)
From: "Xiao Jiang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12623588.1355332630172.1558.1355420172524@arcas>
In-Reply-To: <JIRA.12623588.1355332630172@arcas>
References: <JIRA.12623588.1355332630172@arcas>
Subject: [jira] [Updated] (HIVE-3795) NPE in SELECT when WHERE-clause is an
 and/or/not operation involving null
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xiao Jiang updated HIVE-3795:
-----------------------------

    Attachment: HIVE-3795.1.patch.txt
    
> NPE in SELECT when WHERE-clause is an and/or/not operation involving null
> -------------------------------------------------------------------------
>
>                 Key: HIVE-3795
>                 URL: https://issues.apache.org/jira/browse/HIVE-3795
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Xiao Jiang
>            Assignee: Xiao Jiang
>            Priority: Trivial
>         Attachments: HIVE-3795.1.patch.txt
>
>
> Sometimes users forget to quote date constants in queries. For example, SELECT * FROM some_table WHERE ds >= 2012-12-10 and ds <= 2012-12-12; . In such cases, if the WHERE-clause contains and/or/not operation, it would throw NPE exception. That's because PcrExprProcFactory in ql/optimizer forgot to check null. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira