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.

Sign up for GitHub

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

Jump to bottom

Incorrect query result of match statement #4908

Closed
czpmango opened this issue Nov 21, 2022 · 3 comments
Closed

Incorrect query result of match statement #4908

czpmango opened this issue Nov 21, 2022 · 3 comments
Assignees
@czpmango
Labels
affects/none PR/issue: this bug affects none version. need info Solution: need more information (ex. can't reproduce) priority/hi-pri Priority: high process/fixed Process of bug severity/minor Severity of bug type/bug Type: something is unexpected
Milestone
v3.4.0

Comments

@czpmango
Copy link
Contributor

czpmango commented Nov 21, 2022 •
edited
Loading

Describe the bug (required)
Refer to https://discuss.nebula-graph.com.cn/t/topic/11140/90
The root cause has yet to be located.
At present, it appears from the execution plan that the results(28 rows of AppendVertices) are incorrectly filtered out. if remove the with clause or turn off the optimization rule, the results are inconsistent.
I didn't reproduce it. Need to check the impact of property pruning or other optimization rules. Also need to check if it has been fixed in the latest version.

Your Environments (required)
nebula v3.1.0

How To Reproduce(required)
Not yet reproduced.

Expected behavior
Get the correct query result.
@czpmango czpmango added type/bug Type: something is unexpected priority/hi-pri Priority: high labels Nov 21, 2022
@Sophie-Xie Sophie-Xie added this to the v3.4.0 milestone Nov 21, 2022
@Sophie-Xie Sophie-Xie added the need info Solution: need more information (ex. can't reproduce) label Nov 21, 2022
@wey-gu wey-gu mentioned this issue Nov 26, 2022
Closed
@HarrisChu HarrisChu added affects/none PR/issue: this bug affects none version. severity/none Severity of bug labels Dec 1, 2022
@HarrisChu HarrisChu added the severity/minor Severity of bug label Dec 7, 2022
@github-actions github-actions bot removed the severity/none Severity of bug label Dec 7, 2022
@xtcyclist
Copy link
Contributor

I checked the execution plan provided by the user. There seeems to be no difference that I can spot. Not sure what the root cause is.

I recommend the user to upgrade it to the the 3.4 version later.

@czpmango
Copy link
Contributor Author

I checked the execution plan provided by the user. There seeems to be no difference that I can spot. Not sure what the root cause is.

I recommend the user to upgrade it to the the 3.4 version later.

ACK.

@Sophie-Xie
Copy link
Contributor

Close it first, reopen if it reappears.

@github-actions github-actions bot added the process/fixed Process of bug label Jan 29, 2023
@wey-gu wey-gu mentioned this issue Feb 4, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@czpmango czpmango

Labels
affects/none PR/issue: this bug affects none version. need info Solution: need more information (ex. can't reproduce) priority/hi-pri Priority: high process/fixed Process of bug severity/minor Severity of bug type/bug Type: something is unexpected
Projects
None yet
Milestone
v3.4.0
Development

No branches or pull requests
4 participants
@HarrisChu @xtcyclist @czpmango @Sophie-Xie