What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

We are migrating data from Cassandra to MongoDB and we have many tables with timeuuid fields in Cassandra, which are using UUID version 1. In MongoDB, our UUID data is being mapped to standard UUID values, but UUID version 1 sort order does not match UUID version 4 sort order. As a result, queries that depend on natural ordering by UUID may return different results after migration.

What would you like to see happen?

Describe the desired outcome or enhancement.

We would like MongoDB to support UUID version 1, or provide an equivalent built-in type/representation that preserves time-based ordering semantics, so that Cassandra timeuuid data can be migrated without losing sort behavior or requiring custom application-side workarounds.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

So that the user experience from Cassandra stays intact, and migration to MongoDB doesn't introduce any behavior change.

What steps, if any, are you taking today to manage this problem?

In absence of native support, we would have to introduce additional fields to carry the time component and a tie breaker value. This adds to unwanted extra resource consumption and complexity.