Skip to content
New issue

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

should reset session space after Space not existed #4818

Closed
nebula-bots opened this issue Nov 2, 2022 · 2 comments
Closed

should reset session space after Space not existed #4818

nebula-bots opened this issue Nov 2, 2022 · 2 comments
Assignees
Labels
affects/master PR/issue: this bug affects master version. auto-sync process/done Process of bug severity/minor Severity of bug type/bug Type: something is unexpected wontfix Solution: this will not be worked on recently
Milestone

Comments

@nebula-bots
Copy link
Contributor

there're two session, sessionA and sessionB

  1. sessionA: create spaceA, and then use space.
  2. sessionB: drop the spaceA
  3. sessionA: create tag in spaceA

expected result:

  1. raise a Space not existed error.
  2. the space name in resultSet should be ""

actual result:

  1. raise a Space not existed error.
  2. the space name in resultSet is still "spaceA"

image

space name is still "spaceA"

@nebula-bots nebula-bots added auto-sync type/bug Type: something is unexpected labels Nov 2, 2022
@Aiee Aiee self-assigned this Nov 2, 2022
@Sophie-Xie Sophie-Xie added this to the v3.4.0 milestone Nov 2, 2022
@nebula-bots nebula-bots added severity/minor Severity of bug severity/none Severity of bug labels Nov 5, 2022
@jinyingsunny jinyingsunny removed the severity/none Severity of bug label Nov 11, 2022
@Aiee
Copy link
Contributor

Aiee commented Nov 15, 2022

We might need to add a new error code to distinguish if the SPACE_NOT_FOUND is returned by a USE statement or other statements.

For example, for query like use space_1; create tag t1(), if space_1 was dropped before executing create tag t1(), the session space should be reset. If space_1 was dropped before executing use space_1, the space should remain the same.

This will be regarded as a known issue for now.

@Sophie-Xie Sophie-Xie added the wontfix Solution: this will not be worked on recently label Nov 15, 2022
@Sophie-Xie Sophie-Xie assigned MuYiYong and unassigned Aiee Dec 1, 2022
@HarrisChu HarrisChu added the affects/none PR/issue: this bug affects none version. label Dec 1, 2022
@Sophie-Xie
Copy link
Contributor

Discuss it with @MuYiYong @HarrisChu: we will not fix it.

@github-actions github-actions bot added the process/fixed Process of bug label Dec 5, 2022
@HarrisChu HarrisChu added the process/done Process of bug label Dec 6, 2022
@github-actions github-actions bot removed the process/fixed Process of bug label Dec 6, 2022
@nebula-bots nebula-bots added affects/master PR/issue: this bug affects master version. and removed affects/none PR/issue: this bug affects none version. labels Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/master PR/issue: this bug affects master version. auto-sync process/done Process of bug severity/minor Severity of bug type/bug Type: something is unexpected wontfix Solution: this will not be worked on recently
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants