You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vineet Garg (JIRA)" <ji...@apache.org> on 2018/04/09 20:53:04 UTC
[jira] [Updated] (HIVE-18215) Possible code optimization exists for
"INSERT OVERWITE on MM table. SELECT FROM (SELECT .. UNION ALL SELECT ..)
[ https://issues.apache.org/jira/browse/HIVE-18215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vineet Garg updated HIVE-18215:
-------------------------------
Fix Version/s: (was: 3.0.0)
3.1.0
Deferring this to 3.1.0 since the branch for 3.0.0 has been cut off. Please update the JIRA if you would like to get your patch in 3.0.0.
> Possible code optimization exists for "INSERT OVERWITE on MM table. SELECT FROM (SELECT .. UNION ALL SELECT ..)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-18215
> URL: https://issues.apache.org/jira/browse/HIVE-18215
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 3.0.0
> Reporter: Steve Yeom
> Assignee: Steve Yeom
> Priority: Minor
> Fix For: 3.1.0
>
>
> removeTempOrDuplicateFiles(.) has an opportunity for performance code optimization for the
> test case of "INSERT OVERWITE on MM table. SELECT FROM (SELECT .. UNION ALL SELECT ..)" from dp_counter_mm.q.
> This is MM table specific and we can avoid calling fs.exists() by creating a specific mmDirectories
> list for the current SELECT statement (out of two SELECTs in our test case from
> the dp_counter_mm.q) from the IOW union all query.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)