[
https://issues.apache.org/jira/browse/HIVE-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-2540:
------------------------------
Attachment: HIVE-2540.D2805.1.patch
navis requested code review of "HIVE-2540 [jira] LATERAL VIEW with EXPLODE
produces ConcurrentModificationException".
Reviewers: JIRA
DPAL-1095 LATERAL VIEW with EXPLODE produces ConcurrentModificationException
The following produces ConcurrentModificationException on the for loop inside
EXPLODE:
create table foo as select array(1, 2) a from src limit 1;
select a, x.b from foo lateral view explode(a) x as b;
TEST PLAN
EMPTY
REVISION DETAIL
https://reviews.facebook.net/D2805
AFFECTED FILES
hbase-handler/src/java/org/apache/hadoop/hive/hbase/LazyHBaseCellMap.java
ql/src/test/queries/clientpositive/udf_explode.q
ql/src/test/queries/clientpositive/udtf_explode.q
ql/src/test/results/clientpositive/udf_explode.q.out
ql/src/test/results/clientpositive/udtf_explode.q.out
serde/src/java/org/apache/hadoop/hive/serde2/lazy/LazyArray.java
serde/src/java/org/apache/hadoop/hive/serde2/lazy/LazyMap.java
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/6393/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
> LATERAL VIEW with EXPLODE produces ConcurrentModificationException
> ------------------------------------------------------------------
>
> Key: HIVE-2540
> URL: https://issues.apache.org/jira/browse/HIVE-2540
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.7.1
> Reporter: David Phillips
> Attachments: HIVE-2540.D2805.1.patch
>
>
> The following produces {{ConcurrentModificationException}} on the {{for}}
> loop inside EXPLODE:
> {code}
> create table foo as select array(1, 2) a from src limit 1;
> select a, x.b from foo lateral view explode(a) x as b;
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
