You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 31, 2020. It is now read-only.
Currently we upload records with a prefix including the timestamp in seconds.
S3 returns keys by "UTF-8 binary order", so for example if you put record 0 ".../12340000/z/..." then record 1 ".../12340000/a/..." then record 1 would be returned first.
This impacts the initial sync, when order is important.
We could solve this by storing the timestamp at millisecond precision.
Currently we upload records with a prefix including the timestamp in seconds.
S3 returns keys by "UTF-8 binary order", so for example if you put record 0 ".../12340000/z/..." then record 1 ".../12340000/a/..." then record 1 would be returned first.
This impacts the initial sync, when order is important.
We could solve this by storing the timestamp at millisecond precision.
Related: #49
The text was updated successfully, but these errors were encountered: