hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rui Li (JIRA)" <>
Subject [jira] [Commented] (HIVE-9153) Evaluate CombineHiveInputFormat versus HiveInputFormat [Spark Branch]
Date Fri, 19 Dec 2014 03:51:13 GMT


Rui Li commented on HIVE-9153:

I think we actually can get location info with {{CombineHiveInputFormat}}. I verified this
by running some tests on my machine and most tasks have NODE_LOCAL locality (some has PROCESS_LOCAL
because {{CombineHiveInputFormat.getLocations}} returns null).
BTW, spark prints "PROCESS_LOCAL" for tasks that have no preferred locations, which may be
a bug:
    if (TaskLocality.isAllowed(maxLocality, TaskLocality.NO_PREF)) {
      // Look for noPref tasks after NODE_LOCAL for minimize cross-rack traffic
      for (index <- dequeueTaskFromList(execId, pendingTasksWithNoPrefs)) {
        return Some((index, TaskLocality.PROCESS_LOCAL, false))

> Evaluate CombineHiveInputFormat versus HiveInputFormat [Spark Branch]
> ---------------------------------------------------------------------
>                 Key: HIVE-9153
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>    Affects Versions: spark-branch
>            Reporter: Brock Noland
>            Assignee: Rui Li
>         Attachments: screenshot.PNG
> The default InputFormat is {{CombineHiveInputFormat}} and thus HOS uses this. However,
Tez uses {{HiveInputFormat}}. Since tasks are relatively cheap in Spark, it might make sense
for us to use {{HiveInputFormat}} as well. We should evaluate this on a query which has many
input splits such as {{select count(\*) from store_sales where something is not null}}.

This message was sent by Atlassian JIRA

View raw message