[CAMEL-19470] Exchange body is null when using Mongodb changeStreams with update operation

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.x
• Fix Version/s: 3.21.0, 4.0-RC1, 4.0.0
• Component/s: camel-mongodb
• Labels: camel mongodb
• Estimated Complexity: Moderate
• Flags: Patch

Language

java

• Assignee: Unassigned
• Reporter: Kevin Garrido
• Created: 19/Jun/23 10:31
• Updated: 21/Jun/23 11:37
• Resolved: 21/Jun/23 11:37

Description

When using the mongodb component as a ChangeStreams consumer, the fullDocument is null for update operations. It's normal if we refer to mongodb documentation.

 

As a temporary fix, you can use the object id to get the modified document with a route like this: 

from("mongodb:mongo?consumerType=changeStreams....")
.to("mongodb:mongo?operation=findById")

 

 

The MongoDbChangeStreamsThread.initializeCursor() method should be changed to use the fullDocument option when creating the iterable.

Issue Links

• links to: GitHub Pull Request #10434
• links to: GitHub Pull Request #10435
• links to: GitHub Pull Request #10436