[
https://issues.apache.org/jira/browse/IGNITE-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018085#comment-15018085
]
Ivan Veselovsky commented on IGNITE-1679:
-----------------------------------------
I would suggest to remove the PURGE event at all , until we have a clear
understanding of a use case this kind of event is needed.
Currently we have somewhat inconsistent implementation which is used nowhere
except the tests.
> 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: Ivan Veselovsky
> 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)
