[SERVER-22939] A regular expression with an escaped pipe '|' character is treated as non-simple Created: 03/Mar/16 Updated: 20/Mar/16 Resolved: 20/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | ITWEBTF SAXOBANK | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | See the referenced issues. Note that I see this as critical because this breaks functionality that has worked for years. We depend on this functionality. |
||||||||
| Participants: | |||||||||
| Description |
|
This seems to be a regression from the fix of SERVER-15235. The problem with this fix is that, even when I have a regular expression that has a left-anchor and an escaped '|' character, that query is recognized as being "non-simple". This is wrong, and it causes unnecessarily that backwards compatibility is broken and performance is significantly degraded. See SERVER-22872 and SERVER-22890. |
| Comments |
| Comment by Ramon Fernandez Marina [ 20/Mar/16 ] |
|
If I understand correctly a fix for SERVER-16622 will resolve this issue, so I'm marking this ticket as a duplicate of SERVER-16622. Please let me know if I overlooked something here. Regards, |