[
https://issues.apache.org/jira/browse/IGNITE-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906394#comment-14906394
]
ASF GitHub Bot commented on IGNITE-1515:
----------------------------------------
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/105
Ignite 1515 b
https://issues.apache.org/jira/browse/IGNITE-1515
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite ignite-1515-b
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/105.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #105
----
commit 61859f90130c95f4bb9f4bd721f70e9b067068ef
Author: iveselovskiy <[email protected]>
Date: 2015-09-24T13:24:59Z
1515: workable version, needs cleanup.
commit 7cad4c35bd301d53544ad35a32e2cc7bd1d473e7
Author: iveselovskiy <[email protected]>
Date: 2015-09-24T14:14:16Z
ignite-1515: cleanup.
----
> IGFS: delete operations should be truly thread-safe
> ---------------------------------------------------
>
> Key: IGNITE-1515
> URL: https://issues.apache.org/jira/browse/IGNITE-1515
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Veselovsky
> Assignee: Ivan Veselovsky
>
> In IGNITE-586 we fixed concurrency problem in rename/move operations.
> Since delete is actually also remove, we should fix deletion operations also
> accordingly using similar logic.
> IgfsMetaManager#move0(2) method is to be used partially in delete operation
> -- need to refactor code accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
