You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/03/09 15:47:00 UTC
[jira] [Created] (HADOOP-16176) Add some tests about timestamp
tracking
Steve Loughran created HADOOP-16176:
---------------------------------------
Summary: Add some tests about timestamp tracking
Key: HADOOP-16176
URL: https://issues.apache.org/jira/browse/HADOOP-16176
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/s3, test
Affects Versions: 3.3.0
Reporter: Steve Loughran
We need to make sure we understand timestamp behaviour across S3 implementations, for both single part and multipart uploads
tests to verify that the timestamp of files is consistent
* individual files's timestamps don't appear to change
* if you upload two small files in sequence, the timestamp of file 2> file 1
MPU uploads are different: their timestamp may be that of the upload start, rater than upload delete
A sequence of
# init MPU to file1
# PUT to file 2
# complete MPU to file1
may result in timestamp(file1) < timestamp(file2)
but if you add a PUT to file 0 before step 1, then we require that timestamp(file0) < timestamp(file1). That is: there's still an ordering on initialization.
these tests are probably relevant to all MPU implementations, though they'll offer different timing outcomes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org