Currently, the MongoDB connector used in Copy Activity does not support filtering by _id when the field is of UUID type!!!!!!
This is a critical limitation for any scenario where precise entity-level extraction is required.
In my use case, I’m trying to copy specific documents from MongoDB using a filter like:
{ "_id": UUID("abb0eaa4-bc5a-41ab-89c7-27494a99a9a4") }
or
{ "_id": "abb0eaa4-bc5a-41ab-89c7-27494a99a9a4" }
or
However, neither approach returns any data. I’ve tested multiple formats, and none seem to work. The actual representation of the UUID in MongoDB is:
"_id": { "$binary": { "base64": "q7DqpLxaQauJxydJSpmppA==", "subType": "04" } }
This is a standard UUID subtype (subType: "04"), and filtering by such values should be natively supported. Without this capability, it's impossible to target specific documents for extraction, which severely limits the connector’s usefulness in real-world scenarios.
Request:
Please add support for filtering by UUID in the MongoDB connector. This is not a niche feature - it’s a basic requirement for working with MongoDB collections that use UUIDs as primary keys.
Support request ID: 2507241420001713
Thank you for considering this request.
