Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <27990317.2781271096989766.JavaMail.jira@thor>
Date: Mon, 12 Apr 2010 14:29:49 -0400 (EDT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1011) GenericUDTFExplode() throws NPE when
 given nulls
In-Reply-To: <980466609.1261611569394.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856106#action_12856106 ] 

Namit Jain commented on HIVE-1011:
----------------------------------

I think 3. makes most sense - I will take a look at the patch

> GenericUDTFExplode() throws NPE when given nulls
> ------------------------------------------------
>
>                 Key: HIVE-1011
>                 URL: https://issues.apache.org/jira/browse/HIVE-1011
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Paul Yang
>            Assignee: Paul Yang
>         Attachments: HIVE-1011.1.patch
>
>
> When explode() is called on rows where the array column is null, a null pointer exception is thrown.
> For example consider having  a table named test with the following rows
> {code}
> key     value
> 1       [1,2,3]
> 2       null 
> {code}
> Then running the query
> {code}
> SELECT explode(value) AS myCol FROM test;
> or
> SELECT * FROM test LATERAL VIEW explode(value) myTab AS myCol;
> {code}
> will throw a null pointer exception when explode() gets the null value from the 2nd row.
> Possible options are:
> 1. Treat null values as an error and make the user fix null values in data
> 2. explode(null) generates a null output value.
> 3. explode(null) generates no output values
> #2 means that explode(null) and explode(array(null)) will behave identically. Because of that, I think #3 makes the most sense.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira