hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Perroud (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6634) inotify in HDFS
Date Tue, 31 Mar 2015 14:50:56 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388642#comment-14388642
] 

Benoit Perroud commented on HDFS-6634:
--------------------------------------

We started to migrate our code to this implementation. It's just awesome. Thanks a lot [~james.thomas]
for the work!

I still have a quick question: any reason why the transaction id is not embedded in the Event
object?



> inotify in HDFS
> ---------------
>
>                 Key: HDFS-6634
>                 URL: https://issues.apache.org/jira/browse/HDFS-6634
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: hdfs-client, namenode, qjm
>            Reporter: James Thomas
>            Assignee: James Thomas
>             Fix For: 2.6.0
>
>         Attachments: HDFS-6634.2.patch, HDFS-6634.3.patch, HDFS-6634.4.patch, HDFS-6634.5.patch,
HDFS-6634.6.patch, HDFS-6634.7.patch, HDFS-6634.8.patch, HDFS-6634.9.patch, HDFS-6634.patch,
inotify-design.2.pdf, inotify-design.3.pdf, inotify-design.4.pdf, inotify-design.pdf, inotify-intro.2.pdf,
inotify-intro.pdf
>
>
> Design a mechanism for applications like search engines to access the HDFS edit stream.



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

Mime
View raw message