[COMPASS-2095] validation nullable - value equal to null includes value missing Created: 24/Sep/17 Updated: 10/Jan/24 Resolved: 05/Mar/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Document Validation |
| Affects Version/s: | None |
| Fix Version/s: | 1.18.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Related to COMPASS-72 and "Nullable" constraint. In our query language a:null matches documents where field a does not exist. So it's sufficient for Nullable true to have value field:null and exists:false is redundant when equality with null is present. |
| Comments |
| Comment by Massimiliano Marcon [ 05/Mar/19 ] |
|
In 1.18 we introduced a new schema validation experience that completely replaces the old one. The first iteration only includes a smart editor with autocomplete, so this issue is definitely gone away. |