extend condition to also filter by field exists or not #1879
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Filter by condition throws an exception if a field participating in the condition is missing from the instance.

Suggesting here to extend conditions to also handle the very existence of the field in the instance as a measure of this instance being required.
This can be handy for cleaning datasets in some of the cards, which now throw exception for a missing field (breaking the pre-processing pipeline), and also, indirectly, shed light on cards that are totally erroneous, and are better be removed from the catalog:
E.g. for helpful cleaning:
Currently:
whereas pushing the new operators in the card, yields:
Another example, that makes us consider a removal of a totally erroneous card from the catalog:

while with the new filter, we find that the whole subset is missing that field, and we may want to remove the card (for subset 'experts') from the catalog altogether:
Just to prove the point that the whole dataset, of subset experts, does not match the preprocessing steps:

as compared to a subset that does match:
