You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/10/17 00:18:44 UTC

[jira] [Resolved] (HDFS-5096) Automatically cache new data added to a cached path

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

Colin Patrick McCabe resolved HDFS-5096.
----------------------------------------

          Resolution: Fixed
       Fix Version/s: HDFS-4949
    Target Version/s: HDFS-4949

thanks for the reviews, Andrew and Chris.

> Automatically cache new data added to a cached path
> ---------------------------------------------------
>
>                 Key: HDFS-5096
>                 URL: https://issues.apache.org/jira/browse/HDFS-5096
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Andrew Wang
>            Assignee: Colin Patrick McCabe
>             Fix For: HDFS-4949
>
>         Attachments: HDFS-5096-caching.002.patch, HDFS-5096-caching.005.patch, HDFS-5096-caching.006.patch, HDFS-5096-caching.009.patch, HDFS-5096-caching.010.patch, HDFS-5096-caching.011.patch, HDFS-5096-caching.012.patch, HDFS-5096-caching.014.patch
>
>
> For some applications, it's convenient to specify a path to cache, and have HDFS automatically cache new data added to the path without sending a new caching request or a manual refresh command.
> One example is new data appended to a cached file. It would be nice to re-cache a block at the new appended length, and cache new blocks added to the file.
> Another example is a cached Hive partition directory, where a user can drop new files directly into the partition. It would be nice if these new files were cached.
> In both cases, this automatic caching would happen after the file is closed, i.e. block replica is finalized.



--
This message was sent by Atlassian JIRA
(v6.1#6144)