[SERVER-57073] Robustify indexed_insert_text.js in read concern: local write concern: 1 scenario Created: 19/May/21 Updated: 29/Oct/23 Resolved: 20/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Query Execution |
| Affects Version/s: | 4.9.0-alpha4 |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Yoon Soo Kim | Assignee: | Yoon Soo Kim |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Query Execution 2021-05-31 | ||||
| Participants: | |||||
| Linked BF Score: | 44 | ||||
| Description |
|
indexed_insert_text.js test suite main verification logic depends on the guarantee that the text index is created and visible to other transaction but due to read concern/write concern combination, it's not visible. The simplest fix on top of my head is to wait for the text index to be visible using getIndexes().
|
| Comments |
| Comment by Githook User [ 20/May/21 ] |
|
Author: {'name': 'Yoonsoo Kim', 'email': 'yoonsoo.kim@mongodb.com', 'username': 'yun-soo'}Message: |
| Comment by Yoon Soo Kim [ 20/May/21 ] |
|
CR is out: https://mongodbcr.appspot.com/773260022/ |