You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Trino with the Mongodb, when filtering on most primitive type fields can pushdown to mongo and has good performance. However, filtering on the array field will lead to a table scan and poor performance.
I am working on an improvement to pushdown the "contains" function to MongoDB. So when SQL has conditions like WHERE contains(colArray, -1), trino can pushdown to mongo using {"colArray": -1} to filter documents.
The text was updated successfully, but these errors were encountered:
When using Trino with the Mongodb, when filtering on most primitive type fields can pushdown to mongo and has good performance. However, filtering on the array field will lead to a table scan and poor performance.
I am working on an improvement to pushdown the "contains" function to MongoDB. So when SQL has conditions like
WHERE contains(colArray, -1)
, trino can pushdown to mongo using{"colArray": -1}
to filter documents.The text was updated successfully, but these errors were encountered: