ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Veselovsky (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-1679) IGFS: Purge event is inconsistent.
Date Wed, 25 Nov 2015 12:56:10 GMT

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

Ivan Veselovsky edited comment on IGNITE-1679 at 11/25/15 12:55 PM:
--------------------------------------------------------------------

https://github.com/apache/ignite/pull/262

Fixed: now PURGE events fired for all disappearing files.


was (Author: iveselovskiy):
https://github.com/apache/ignite/pull/262

> IGFS: Purge event is inconsistent.
> ----------------------------------
>
>                 Key: IGNITE-1679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1679
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.5
>
>
> Currently PURGE event is fired only to files which were deleted explicitly. It is not
fired which are deleted as a part of recursive deletion of parent directory.
> To fix that we should set the last known entry path when moving it to trash. This way
we will be able to calculate path for each removed child entry.
> Another question is do we really need to fire events for child entries. Or we should
only fire them for the target entries.



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

Mime
View raw message