[
https://issues.apache.org/jira/browse/HDFS-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390537#comment-14390537
]
Benoit Perroud commented on HDFS-6634:
--------------------------------------
[~cmccabe] you probably meant {{EventList}}. But this class is not available
outside of {{DFSInotifyEventInputStream}}, i.e. {{poll}} and {{take}} both
return {{Event}} which does not contains the txid.
I understand CONCAT_DELETE for instance can have multiple {{Event}}s with the
same txId, but from my perspective the txId should be embedded in the
{{Event}}. There's no easy way to compute it otherwise apart from incrementing
a counter.
> 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)
