albertogpz commented on pull request #6200:
URL: https://github.com/apache/geode/pull/6200#issuecomment-814834421
> > We had a small impromtu discussion with the query engine team and some
research on how NoSQL treats null (or nil in some worlds)
> > ```
> > * in MongoDB we founnd that
> > `The { item : null } query matches documents that either contain the
item field whose value is null or that do not contain the item field.`
> >
> > * in redis nil is returned if the field does not exist.
> > ```
> >
> >
> > Hence we think that the current behavior i.e. querying without indexes
is the right result and we should try to make the indexes return the same
result.
>
> @nabarunnag Thanks for your comments. If @agingade agrees (I will check
his answers after having provided mine to his comments) I will look into this
possibility.
@nabarunnag and @agingade : I have created a new pull request with a
solution in which I keep the current behavior of the queries without indexes:
https://github.com/apache/geode/pull/6279
Please, dismiss this PR and check the new one.
I have not been able to find a complete solution for the "allkeys" type of
index (e.g. positions[*]) and with the solution, queries with this type of
index and queries of type "!=" or comparing to null will not use the index even
if configured. This is a limitation that could be tackled in a future PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
