[SERVER-84829] Investigate performance impact of Bison error reporting Created: 22/Sep/20 Updated: 13/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Zolnierz | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Sprint: | Query 2020-10-05 |
| Participants: |
| Description |
|
In particular, we're currently setting the error verbosity to 'verbose' which generates useful error messages (e.g. unexpected <x> token, expected either <y> or <z>). There's also the 'parse.assert' bison declaration which may be worth toggling. |