We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug (required)
Statement drop tag index deletes the edge index unexpectedly, and vice versa for the deletion of the tag index.
drop tag index
Your Environments (required) Version: v2.6 and previous versions
How To Reproduce(required)
(root@nebula) [nba]> create tag A(a int) Execution succeeded (time spent 2126/2508 us) (root@nebula) [nba]> create edge E(a int) Execution succeeded (time spent 2039/2379 us) (root@nebula) [nba]> create tag index a_index on A(a) Execution succeeded (time spent 1959/2310 us) (root@nebula) [nba]> create edge index e_index on E(a) Execution succeeded (time spent 2097/2452 us) (root@nebula) [nba]> drop tag index e_index Execution succeeded (time spent 1572/1963 us) (root@nebula) [nba]> drop edge index a_index Execution succeeded (time spent 1702/2114 us)
Expected behavior
An error should be reported when trying to delete an edge index with statement drop tag index e_index, and vice versa.
drop tag index e_index
Additional context Maybe we should reconsider similar grammatical design to avoid ambiguity and unfriendliness to users.
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
czpmango
Successfully merging a pull request may close this issue.
Describe the bug (required)
Statement
drop tag index
deletes the edge index unexpectedly, and vice versa for the deletion of the tag index.Your Environments (required)
Version: v2.6 and previous versions
How To Reproduce(required)
Expected behavior
An error should be reported when trying to delete an edge index with statement
drop tag index e_index
, and vice versa.Additional context
Maybe we should reconsider similar grammatical design to avoid ambiguity and unfriendliness to users.
The text was updated successfully, but these errors were encountered: