Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 18 Feb 2014 00:27:20 +0000 (UTC)
From: "Brock Noland (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12436898.1254296781430.55138.1392683240132@arcas>
In-Reply-To: <JIRA.12436898.1254296781430@arcas>
References: <JIRA.12436898.1254296781430@arcas>
Subject: [jira] [Updated] (HIVE-860) Persistent distributed cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brock Noland updated HIVE-860:
------------------------------

    Attachment: HIVE-860.patch

I tested manually on a cluster but I am sure tests will be impacted by this change. Let's see.

https://reviews.apache.org/r/18200/

> Persistent distributed cache
> ----------------------------
>
>                 Key: HIVE-860
>                 URL: https://issues.apache.org/jira/browse/HIVE-860
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 0.12.0
>            Reporter: Zheng Shao
>            Assignee: Brock Noland
>             Fix For: 0.13.0
>
>         Attachments: HIVE-860.patch
>
>
> DistributedCache is shared across multiple jobs, if the hdfs file name is the same.
> We need to make sure Hive put the same file into the same location every time and do not overwrite if the file content is the same.
> We can achieve 2 different results:
> A1. Files added with the same name, timestamp, and md5 in the same session will have a single copy in distributed cache.
> A2. Filed added with the same name, timestamp, and md5 will have a single copy in distributed cache.
> A2 has a bigger benefit in sharing but may raise a question on when Hive should clean it up in hdfs.


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