Hello I was looking at this pr: https://github.com/airbytehq/airbyte/pull/61370/commits/928cc4bf832ad5f83800358deb9fd6750d44d35b - upgrading the debezium version for mongodb-source-v2 was not merged. It seems to address an issue that causes unwanted resource usage when the buffer queue is full. This would be nice to have - and we investigated doing it ourselves. However, I saw in debezium > 2.7.0 debezium saves everything in bson. This seems to be a breaking change for the connector as it causes errors such as

io.airbyte.cdk.integrations.source.relationaldb.state.FailedRecordIteratorException: java.lang.IllegalArgumentException: Non-hex character 'M' at index=0

. Any suggestions on how to tackle this problem?

I'm sorry, but the knowledge sources do not contain enough information to provide a definitive answer to your question about upgrading Debezium to >2.7.0 for the MongoDB source connector and handling the BSON serialization change. From the available sources, I can confirm that there have been discussions and some upgrades of Debezium in the Airbyte MongoDB source v2 connector (for example, to 2.6.2 in version 1.4.0 and to 2.5.1 in version 1.3.12), but there is no documentation or discussion about handling the breaking change introduced in Debezium >2.7.0 where everything is saved in BSON, nor about the specific error you mentioned (

Non-hex character 'M' at index=0

) or strategies to address it in Airbyte's codebase. The changelogs and issues do not mention any adaptation or workaround for this BSON serialization change or related migration steps for the connector to support Debezium >2.7.0[Changelog](https://docs.airbyte.com/integrations/sources/mongodb-v2#changelog). If you are considering upgrading Debezium yourself, you may need to investigate how Airbyte's MongoDB source connector parses and processes Debezium's output, and adapt it to handle BSON serialization. However, there is no guidance or example of this in the provided knowledge sources. If you need further assistance, I recommend opening a discussion or issue on the Airbyte GitHub repository to get input from the maintainers or community, as this appears to be an advanced and potentially breaking change not yet addressed in the public documentation or changelogs.