albertogpz commented on pull request #6028: URL: https://github.com/apache/geode/pull/6028#issuecomment-789073349
> Usually the queries that don't have indexes are considered "correct" and the ones with indexes usually were checked against those results. > Was the issue due to the map index not mapping values it didn't know about? > > A solution down the line might be to allow custom indexing. > > Is there a way to disable the != only for queries that use the map index? Queries that use the base compact range index should still be able to execute != in a timely fashion. I created the test in order to compare queries with and without indexes. Nevertheless, I think that currently queries without indexes do not give the right results with where clauses in which the map for the key passed is compared with null, for example: "positions['SUN'] != null" or "positions['SUN'] = null. In these cases for entries that contain the map (positions != null) but positions does not contain the "SUN" key, it considers that positions['SUN'] is null. I have changed the code in the latest commits to work the way I expected. Besides, I have added a change so that indexes are used again when using CompactRangeIndexes but not when using CompactMapRangeIndexes. There's only 3 test cases that are failing and I still need to investigate. ---------------------------------------------------------------- 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]
