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
I'm working on a project that involves migrating records older than 10 years. My plan was to use KSUIDs with the original creation dates of these records. However, the hardcoded epochStamp starting in 2017 prevents this. I relied on the internal KSUID timestamp to query specific database partitions, which I can't do now due to this limitation (I could still do it but one partition where old records fall would be more populated that the rest).
Would it be possible to allow customization of epochStamp through a PR? If not, should I reconsider using KSUIDs for historical records?
The text was updated successfully, but these errors were encountered:
I'm working on a project that involves migrating records older than 10 years. My plan was to use KSUIDs with the original creation dates of these records. However, the hardcoded epochStamp starting in 2017 prevents this. I relied on the internal KSUID timestamp to query specific database partitions, which I can't do now due to this limitation (I could still do it but one partition where old records fall would be more populated that the rest).
Would it be possible to allow customization of
epochStamp
through a PR? If not, should I reconsider using KSUIDs for historical records?The text was updated successfully, but these errors were encountered: