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

How do we define empty value #4942

Closed
czpmango opened this issue Nov 29, 2022 · 5 comments
Closed

How do we define empty value #4942

czpmango opened this issue Nov 29, 2022 · 5 comments
Assignees
Labels
affects/none PR/issue: this bug affects none version. process/done Process of bug severity/none Severity of bug type/bug Type: something is unexpected wontfix Solution: this will not be worked on recently
Milestone

Comments

@czpmango
Copy link
Contributor

Describe the bug (required)
We need to define the exact semantics of empty and null to avoid inconsistent statement behavior.

Your Environments (required)
nebula all versions

How To Reproduce(required)

(root@nebula) [nba]> go from "Tim Duncan" over * yield $$.team.name
+--------------+
| $$.team.name |
+--------------+
|              |
|              |
| "Spurs"      |
|              |
|              |
|              |
|              |
+--------------+
Got 7 rows (time spent 3690/4030 us)

(root@nebula) [nba]> match (v)-[]->(n) where id(v)=="Tim Duncan" return n.team.name
+-------------+
| n.team.name |
+-------------+
| "Spurs"     |
| __NULL__    |
| __NULL__    |
| __NULL__    |
| __NULL__    |
| __NULL__    |
| __NULL__    |
+-------------+

Expected behavior
The expectation is to ensure consistent behavior of statements

Additional context
Similarly, there are other null-compatible value types to consider, such as UNKNOWN_PROP, etc.

@czpmango czpmango added the type/bug Type: something is unexpected label Nov 29, 2022
@czpmango
Copy link
Contributor Author

@MuYiYong cc

@czpmango
Copy link
Contributor Author

@yixinglu cc

@Sophie-Xie Sophie-Xie added this to the v3.4.0 milestone Nov 29, 2022
@HarrisChu HarrisChu added affects/none PR/issue: this bug affects none version. severity/none Severity of bug labels Dec 1, 2022
@xtcyclist
Copy link
Contributor

This is a good issue. It has broad impacts. Need to make an conclusion on this.

@Sophie-Xie Sophie-Xie added need to discuss Solution: issue or PR without a clear conclusion on whether to handle it wontfix Solution: this will not be worked on recently and removed need to discuss Solution: issue or PR without a clear conclusion on whether to handle it labels Dec 5, 2022
@Sophie-Xie
Copy link
Contributor

Discuss it offline with @MuYiYong @yixinglu @HarrisChu: Remain current behavior.

@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 5, 2022
@github-actions github-actions bot removed the process/fixed Process of bug label Dec 5, 2022
@czpmango
Copy link
Contributor Author

czpmango commented Dec 8, 2022

Discuss it offline with @MuYiYong @yixinglu @HarrisChu: Remain current behavior.

Ok.

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. process/done Process of bug severity/none Severity of bug type/bug Type: something is unexpected wontfix Solution: this will not be worked on recently
Projects
None yet
Development

No branches or pull requests

5 participants