'match' not operating as expected within watch(pipeline) functionality on nested fields

Hey @christohill,

I was told by a MongoDB staff member that it was a feature limitation, rather than a bug! I don’t have the level of paid service with Mongo for specific queries to be answered, but a sales rep chased it up for me and mentioned it wasn’t a bug.

I suspect still that it’s a bug but that was the information I was told.

Here a solution for nested field meta_data.status

I continue to search a solution for array, I have exactly the same problem of you @Paul_Chynoweth

1 Like