The profile_operation_metrics.js test currently fails when run with CQF enabled because the docBytesRead metric for read operations using cqf are reported as higher than tests expect. The reason is twofold: 1) sometimes bonsai chooses a collscan when an index scan is expected by the test, and 2) when we use the sampling CE mode (the current default mode), this can increase the docBytesRead metric for the entire query.

We should consider whether we want to change the existing test or add a new test which can give us resource consumption metric coverage for CQF.