[SERVER-51674] Filter out $where clauses in the find and distinct cmds for lock free reads Created: 15/Oct/20 Updated: 27/Oct/23 Resolved: 12/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Henrik Edin |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The $where operator causes the find cmd to use a DBDirectClient under the hood. We are not supporting lock free usage of the DBDirectClient. It's thought that the distinct cmd can also take a $where operator. I did not confirm this, so it should probably be confirmed, and we should check the other cmds that will be in lock-free reads. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 12/Nov/20 ] |
|
Closing in favor of |
| Comment by Geert Bosch [ 12/Nov/20 ] |
|
I believe this can be closed now that we should be able to handle these, right? |