hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7446) HDFS inotify should have the ability to determine what txid it has read up to
Date Tue, 08 Sep 2015 23:25:46 GMT

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

Vinod Kumar Vavilapalli updated HDFS-7446:
------------------------------------------
    Fix Version/s: 2.6.1

Okay, I pulled this into 2.6.1 given the class was marked public unstable (it is marked so
even now on branch-2!) and given your comments above.

The patch didn't apply cleanly, there were import and merge conflicts. Fixed them, ran compilation
and TestDFSInotifyEventInputStream before the push.

> HDFS inotify should have the ability to determine what txid it has read up to
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-7446
>                 URL: https://issues.apache.org/jira/browse/HDFS-7446
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client
>    Affects Versions: 2.6.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0, 2.6.1
>
>         Attachments: HDFS-7446.001.patch, HDFS-7446.002.patch, HDFS-7446.003.patch
>
>
> HDFS inotify should have the ability to determine what txid it has read up to.  This
will allow users who want to avoid missing any events to record this txid and use it to resume
reading events at the spot they left off.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message