You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug (required)
The Match statement gets the wrong result in some indexing cases.
Your Environments (required)
nebula v3.0.0
How To Reproduce(required)
(root@nebula) [nba]> create tag index player_age_index on player(age)
(root@nebula) [nba]> rebuild tag index player_age_index
(root@nebula) [nba]> show tag indexes
+-----------------------+------------+----------+
| Index Name | By Tag | Columns |
+-----------------------+------------+----------+
| "player_age_index" | "player" | ["age"] |
+-----------------------+------------+----------+
Got 3 rows (time spent 529/833 us)
(root@nebula) [nba]>MATCH (v:player) WHERE v.player.name<="Aron Baynes" or v.player.name>"Yao Ming" or v.player.name=="Kobe Bryant" or v.player.age>40 RETURN count(*)
+----------+
| count(*) |
+----------+
| 56 |
+----------+
Got 1 rows (time spent 11032/11276 us)
(root@nebula) [nba]> create tag index player_name_index on player(name(8))
(root@nebula) [nba]> rebuild tag index player_name_index
(root@nebula) [nba]> show tag indexes
+-----------------------+------------+----------+
| Index Name | By Tag | Columns |
+-----------------------+------------+----------+
| "player_age_index" | "player" | ["age"] |
| "player_name_index" | "player" | ["name"] |
+-----------------------+------------+----------+
(root@nebula) [nba]> MATCH (v:player) WHERE v.player.name<="Aron Baynes" or v.player.name>"Yao Ming" or v.player.name=="Kobe Bryant" or v.player.age>40 RETURN count(*)
+----------+
| count(*) |
+----------+
| 11 |
+----------+
Expected behavior
Basic correct result.
Additional context
Reconsider IndexScanRule's pattern-matching or what to do with redundant Filter plannode which already been embeded into IndexScan.
The text was updated successfully, but these errors were encountered:
Describe the bug (required)
The Match statement gets the wrong result in some indexing cases.
Your Environments (required)
nebula v3.0.0
How To Reproduce(required)
Expected behavior
Basic correct result.
Additional context
Reconsider IndexScanRule's pattern-matching or what to do with redundant
Filter
plannode which already been embeded intoIndexScan
.The text was updated successfully, but these errors were encountered: