<#8919 feature: consider using a sequential UID fo...
# meltano-repo-activity
g
#8919 feature: consider using a sequential UID for a job's run ID Issue created by edgarrmondragon ### Feature scope Other ### Description For example, they currently cause the log directories to be ordered randomly Screenshot showing log dirs sorted lexicographically, which doesn't match the timestamp [Image](https://private-user-images.githubusercontent.com/16805946/388312666-d33311eb-4694-4b7a-97bf-7983ba92a961.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTM3OTcxNjgsIm5iZiI6MTc1Mzc5Njg2OCwicGF0aCI6Ii8xNjgwNTk0Ni8zODgzMTI2NjYtZDMzMzExZWItNDY5NC00YjdhLTk3YmYtNzk4M2JhOTJhOTYxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA3MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNzI5VDEzNDc0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVjMWY3ZWVjYmRjOTIyMjU0NDRiZWJjYjg2Mjk5NzJjNWZhNTMwNTg3MzQ4OGZlYzhlMjNjZmY5OWI0MWVlMDImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.j25su5OrRIKEzjA1N7mkxkEhQJ3AtYUrDifqkCUM_7g) so one has to look at the modification date to figure out the last run Screenshot showing log dirs sorted by timestamp [Image](https://private-user-images.githubusercontent.com/16805946/388313083-5edd4f94-f059-42d0-a002-4dfcbaca9b3d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTM3OTcxNjgsIm5iZiI6MTc1Mzc5Njg2OCwicGF0aCI6Ii8xNjgwNTk0Ni8zODgzMTMwODMtNWVkZDRmOTQtZjA1OS00MmQwLWEwMDItNGRmY2JhY2E5YjNkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA3MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNzI5VDEzNDc0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTAyMmQ3YzRiNzE4NzgyZTNiOWM1ZGJjYWRlMTI1NTUxYTA5M2ZlYmE3NGZjNzY3MjVjZTJlYmZhM2IxZDQwY2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.5AzSr2EgyHuEtBovGn1ltoanP-e82Q949gTsymRJu8E) --- There's a few ways we could do this... ### ULIDs Similar proposal and considerations to #7272. ### UUIDv7
UUID version 7 features a time-ordered value field derived from the widely implemented and well known Unix Epoch timestamp source, the number of milliseconds seconds since midnight 1 Jan 1970 UTC, leap seconds excluded. As well as improved entropy characteristics over versions 1 or 6.1
UUIDv82 will already be making it into Python 3.14, and hopefully also UUIDv63 and UUIDv74 will make it. In the meantime, there are third-party implementations like aminalaee/uuid-utils. It's worth noting that the implementation in python/cpython#121119 aims at compatibility with other language implementations: python/cpython#89083 (comment). ## Footnotes 1. https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-04.html#name-uuid-version-7 ↩️ 2. https://github.com/python/cpython/pull/123224 ↩️ 3. https://github.com/python/cpython/pull/120650 ↩️ 4. https://github.com/python/cpython/pull/121119 ↩️ meltano/meltano