When geo indexes and other indexes are on a tag/edge type, the services will crash because it may wrongly choose a non-geo index for a geo-related query.
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
[ ] Unit test(positive and negative cases)
[ ] Function test
[ ] Performance test
[ ] N/A
Affects:
[ ] Documentation affected (Please add the label if documentation needs to be modified.)
[ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.）
[ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
[ ] Performance impacted: Consumes more CPU/Memory
Release notes:
Please confirm whether to be reflected in release notes and how to describe:
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
Fix https://github.com/vesoft-inc/nebula/issues/5919
Description:
When geo indexes and other indexes are on a tag/edge type, the services will crash because it may wrongly choose a non-geo index for a geo-related query.
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
Affects:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: