hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joydeep Sen Sarma (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HIVE-467) Scratch data location should be on different filesystems for different types of intermediate data
Date Fri, 15 May 2009 06:46:45 GMT

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

Joydeep Sen Sarma updated HIVE-467:

    Attachment: hive-467.3.patch

- contains one more fix in ExecDriver where addinputpaths was not using the right filesystem
- removed the system.out.println
- don't want to change insertexternal - i wanted the test to specifically cover the case where
the partition location is specified to external fs (and the table isn't - which means it has
a default location). the suggested test would have actually passed the old code.
- Fixed Hive.java to not create partition first. 

i didn't read carefully through 488 and other jiras. it seems that hive.java's behavior is
exactly the way it is in trunk now except handling the external partition case correctly.
if there are other issues with the current code path - we can fix them through a separate

> Scratch data location should be on different filesystems for different types of intermediate
> -------------------------------------------------------------------------------------------------
>                 Key: HIVE-467
>                 URL: https://issues.apache.org/jira/browse/HIVE-467
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>         Environment: S3/EC2
>            Reporter: Joydeep Sen Sarma
>            Assignee: Joydeep Sen Sarma
>         Attachments: hive-467.3.patch, hive-467.patch.1, hive-467.patch.2
> Currently Hive uses the same scratch directory/path for all sorts of temporary and intermediate
data. This is problematic:
> 1. Temporary location for writing out DDL output should just be temp file on local file
system. This divorces the dependence of metadata and browsing operations on a functioning
hadoop cluster.
> 2. Temporary location of intermediate map-reduce data should be the default file system
(which is typically the hdfs instance on the compute cluster)
> 3. Temporary location for data that needs to be 'moved' into tables should be on the
same file system as the table's location (table's location may not be same as hdfs instance
of processing cluster).
> ie. - local storage, map-reduce intermediate storage and table storage should be distinguished.
Without this distinction - using hive on environments like S3/EC2 causes problems. In such
an environment - i would like to be able to:
> - do metadata operations without a provisioned hadoop cluster (using data stored in S3
and metastore on local disk)
> - attach to a provisioned hadoop cluster and run queries
> - store data back in tables that are created over s3 file system

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message