Fix errors caused by predicates pushdown on MongoDB JSON columns

[silly-carbon]

Description

Fix errors caused by predicates pushdown on MongoDB JSON columns

Is this change a fix, improvement, new feature, refactoring, or other?
fix

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)
This is a change to the MongoDB connector only

How would you describe this change to a non-technical end user or system administrator?
The MongoDB connector no longer causes errors on predicates on JSON columns

Related issues, pull requests, and links

• Fixes Predicates on JSON column fails in MongoDB connector #13536
• Related documentation: None needed

Documentation

( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
( ) Release notes entries required with the following suggested text:

# MongoDB
* Fix failure for queries filtering on columns with `json` type. ({issue}`13536`)

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[ebyhr]

Could you change the commit title and body to

Disable predicate pushdown on MongoDB json columns

The query failed when building MongoDB query.

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[silly-carbon]

@ebyhr Hello there, I've made some updates(according to your previous comments) to the code and wish to get your feedback😁

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[silly-carbon]

@ebyhr Thanks for the comments, I've updated the code.

By the way, please take a look at the CLA mailbox, I believe I've sent a signed PDF 😁

[ebyhr]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[ebyhr]

Could you confirm CI failures?

[silly-carbon]

Could you confirm CI failures?

@ebyhr
Failures solved.

Made changes to io.trino.plugin.mongodb.MongoMetadata#applyFilter to explicitly distinguish between supported and unsupported types

[ebyhr]

Merged, thanks!