-
Notifications
You must be signed in to change notification settings - Fork 5
Preserve mtime after TUS upload #174
Comments
Just Touch the file. eos uses the inode and mtime to calculate the etag (but the etag can also be set, so restoring backups works without changing all etags). the owncloud storage driver implments setting arbitrary metadata and touches the file when the eos driver currently does not support setting arbitrary metadata ... 😞 |
raised here: https://github.com/owncloud/ocis-reva/issues/189 |
I've added to the MVP project as mtime preservation was already on the roadmap |
|
PR for the non-chunked scenarios: cs3org/reva#823 |
Raised #273 for adding related API test |
PR for propagating mtime in chunked mode: cs3org/reva#841 |
|
@PVince81 this is closed but tests are not enabled yet. reopen, or is there an other ticket? |
the PR you have mentioned is only for the public link upload, for normal upload the PRs are |
this is the actual ticket: #273 |
For a PUT request it was always possible to pass in a header "X-OC-Mtime" to specify the mtime of the uploaded file.
Since the addition of TUS upload, Phoenix is already sending the mtime in the Upload-Metadata metadata, but that value is not passed along.
Now I'm not sure whether we store it as "arbitrary metadata" there or whether there is another way streamlined with the storage (like
touch
)@butonic
The text was updated successfully, but these errors were encountered: