Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add cp and cp_rm transfer implementations (rebased onto dev_5_0) #3379

Merged
merged 7 commits into from Jan 26, 2015

Conversation

joshmoore
Copy link
Member

This is the same as gh-3335 but rebased onto dev_5_0.


As suggested by Niko on the forums, cp and cp_rm
implementations make local transfer of files possible
even across filesystem boundaries. The trade-off is
of course that in the case of a failed transfer there
will be increased space used which will need to be
manually cleaned up.

See: https://www.openmicroscopy.org/community/viewtopic.php?f=5&t=7699

/cc @ximenesuk

As suggested by Niko on the forums, cp and cp_rm
implementations make local transfer of files possible
even across filesystem boundaries. The trade-off is
of course that in the case of a failed transfer there
will be increased space used which will need to be
manually cleaned up.

See: https://www.openmicroscopy.org/community/viewtopic.php?f=5&t=7699
All non-upload transfer mechanisms were leaving the
file size in the database set to the size of the UUID
file (36 bytes). By re-checking the file size, the new
isModified method can prevent this.
@joshmoore
Copy link
Member Author

--rebased-from #3335

@ximenesuk
Copy link
Contributor

This all looks good to merge.

@joshmoore
Copy link
Member Author

joshmoore added a commit that referenced this pull request Jan 26, 2015
Add cp and cp_rm transfer implementations (rebased onto dev_5_0)
@joshmoore joshmoore merged commit 56bb583 into ome:dev_5_0 Jan 26, 2015
@sbesson sbesson added this to the 5.0.7 milestone Feb 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants