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

Return value is Empty set #4834

Closed
llinzhe opened this issue Nov 7, 2022 · 5 comments
Closed

Return value is Empty set #4834

llinzhe opened this issue Nov 7, 2022 · 5 comments
Assignees
Labels
affects/none PR/issue: this bug affects none version. need info Solution: need more information (ex. can't reproduce) process/done Process of bug severity/none Severity of bug type/bug Type: something is unexpected
Milestone

Comments

@llinzhe
Copy link

llinzhe commented Nov 7, 2022

Describe the bug (required)
When the session does not select the graph space, using the graph space selection statement and data query statement, the return value is null.

Your Environments (required)

  • OS: centos 7
  • Compiler: g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
    How To Reproduce(required)

Steps to reproduce the behavior:

(root@nebula) [(none)]> :param p0 => 'account001';
(root@nebula) [(none)]> yield $p0
+--------------+
| $p0          |
+--------------+
| "account001" |
+--------------+
Got 1 rows (time spent 325/768 us)

(root@nebula) [(none)]> use userProfile;  MATCH (n1: account)-[r: login*2]-( n2: account) WHERE  n1.account.accountUuid ==$p0  RETURN n2.account.accountUuid as accountUuid
+-------------+
| accountUuid |
+-------------+
+-------------+

Expected behavior
I expect the graph space selection statement to be executed along with the data query statement and return the query result

Additional context
nebula-core:3.3

@llinzhe llinzhe added the type/bug Type: something is unexpected label Nov 7, 2022
@wey-gu
Copy link
Contributor

wey-gu commented Nov 8, 2022

Interesting, I cannot reproduce in 3.2.0

(root@nebula) [test]> use basketballplayer;match (n:`player`) where n.player.name == "Tim Duncan" return *
+----------------------------------------------------+
| n                                                  |
+----------------------------------------------------+
| ("player100" :player{age: 42, name: "Tim Duncan"}) |
| ("player700" :player{age: 42, name: "Tim Duncan"}) |
+----------------------------------------------------+
Got 2 rows (time spent 7228/13821 us)

Tue, 08 Nov 2022 15:06:44 CST

(root@nebula) [basketballplayer]> :param p0 => 'Tim Duncan';
(root@nebula) [basketballplayer]> use basketballplayer;yield $p0
+--------------+
| $p0          |
+--------------+
| "Tim Duncan" |
+--------------+
Got 1 rows (time spent 1819/9157 us)

Tue, 08 Nov 2022 15:07:06 CST

(root@nebula) [basketballplayer]> use basketballplayer;match (n:`player`) where n.player.name == $p0 return *
+----------------------------------------------------+
| n                                                  |
+----------------------------------------------------+
| ("player700" :player{age: 42, name: "Tim Duncan"}) |
| ("player100" :player{age: 42, name: "Tim Duncan"}) |
+----------------------------------------------------+
Got 2 rows (time spent 8026/15345 us)

(root@nebula) [basketballplayer]> use test
Execution succeeded (time spent 1312/16520 us)

Tue, 08 Nov 2022 15:12:59 CST

(root@nebula) [test]> use basketballplayer;match (n:`player`) where n.player.name == $p0 return *
+----------------------------------------------------+
| n                                                  |
+----------------------------------------------------+
| ("player700" :player{age: 42, name: "Tim Duncan"}) |
| ("player100" :player{age: 42, name: "Tim Duncan"}) |
+----------------------------------------------------+
Got 2 rows (time spent 6355/13269 us)

Tue, 08 Nov 2022 15:13:02 CST

@czpmango czpmango self-assigned this Nov 8, 2022
@Sophie-Xie Sophie-Xie added this to the v3.4.0 milestone Nov 8, 2022
@xtcyclist xtcyclist added the type/bug/correctness Query runs normaly but produces wrong results. label Nov 9, 2022
@jinyingsunny jinyingsunny added the severity/major Severity of bug label Nov 10, 2022
@HarrisChu HarrisChu added the affects/none PR/issue: this bug affects none version. label Dec 1, 2022
@czpmango
Copy link
Contributor

czpmango commented Dec 7, 2022

I cannot reproduce it.

@wey-gu
Copy link
Contributor

wey-gu commented Dec 12, 2022

ping @llinzhe , any more context on how to reproduce it?

@xtcyclist xtcyclist added need info Solution: need more information (ex. can't reproduce) and removed severity/major Severity of bug type/bug/correctness Query runs normaly but produces wrong results. labels Dec 12, 2022
@github-actions github-actions bot added the severity/none Severity of bug label Dec 12, 2022
@llinzhe
Copy link
Author

llinzhe commented Dec 12, 2022

That's all there is.

@Sophie-Xie
Copy link
Contributor

Sorry. We can't reproduce it, will close it. If you have some new info, open it again. Thanks.

@github-actions github-actions bot added the process/fixed Process of bug label Dec 27, 2022
@Hester-Gu Hester-Gu added the process/done Process of bug label Jan 13, 2023
@github-actions github-actions bot removed the process/fixed Process of bug label Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/none PR/issue: this bug affects none version. need info Solution: need more information (ex. can't reproduce) process/done Process of bug severity/none Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

8 participants