Skip to content

Conversation

blake-bauman
Copy link

When moving data between different data store types, such as between MongoDB and a SQL database, not all systems have a "_id" as their pimary key. Most often it has a different name or can be multiple keys/columns used as a composite key. This change allows the app to specify an alternate key or a set of keys which, together, can be used as the primary key for a MongoDB insert/update/upsert.

When moving data between different data store types, such as
between MongoDB and a SQL database, not all systems have a
"_id" as their pimary key.  Most often it has a different
name or can be multiple keys/columns used as a composite
key.  This change allows the app to specify an alternate
key or a set of keys which, together, can be used as the
primary key for a MongoDB insert/update/upsert.

Signed-off-by: blake_bauman <[email protected]>
@blake-bauman
Copy link
Author

@fmbenhassine Does this seem reasonable?

@fmbenhassine
Copy link
Contributor

Yes, and the change is backward compatible. Thank you for the PR!

I will plan this for v6.0.0 / v5.2.3.

@fmbenhassine fmbenhassine added this to the 6.0.0 milestone Jul 30, 2025
@fmbenhassine fmbenhassine added pr-for: enhancement in: infrastructure for: backport-to-5.2.x Issues that will be back-ported to the 5.2.x line labels Jul 30, 2025
@blake-bauman
Copy link
Author

Thanks for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: backport-to-5.2.x Issues that will be back-ported to the 5.2.x line in: infrastructure pr-for: enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants