hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HIVE-2939) LazyArray.getList changes array it previously returned
Date Tue, 14 Jan 2014 07:44:51 GMT

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

Navis resolved HIVE-2939.
-------------------------

       Resolution: Duplicate
    Fix Version/s: 0.10.0

Fixed by HIVE-2540 in hive-0.10.0

> LazyArray.getList changes array it previously returned 
> -------------------------------------------------------
>
>                 Key: HIVE-2939
>                 URL: https://issues.apache.org/jira/browse/HIVE-2939
>             Project: Hive
>          Issue Type: Bug
>          Components: UDF
>    Affects Versions: 0.8.1
>            Reporter: Igor Kabiljo
>            Priority: Minor
>             Fix For: 0.10.0
>
>
> Simple query like:
> SELECT a, e
> FROM ikabiljo_test_string_array
> LATERAL VIEW EXPLODE(a) x1 AS e
> (table contains one column - ARRAY<STRING> - and has one row - [b,c,a] )
> fails with ConcurrentModificationException, since LazyArray.getList changes the cached
array it returns.
> LazyArray.getList can easily:
> - return cached array if present, without clearing and refiling. Hive is already not
going to work properly if you change input parameters in an UDF. If that doesn't sound good
- it can return Collections.unmodifiableList
> - or just not cache anything
> Same is true for LazyMap.getMap



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message