You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2015/12/10 09:53:11 UTC

[jira] [Updated] (IGNITE-1679) IGFS: Purge event is inconsistent.

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

Vladimir Ozerov updated IGNITE-1679:
------------------------------------
    Fix Version/s:     (was: 1.5)
                   1.6

> 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.6
>
>
> 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)