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

Fix the bad type evaluated from AttributeExpression on vertices #5151

Merged
merged 7 commits into from
Dec 30, 2022

Conversation

xtcyclist
Copy link
Contributor

@xtcyclist xtcyclist commented Dec 29, 2022

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

Close https://github.com/vesoft-inc/nebula-ent/issues/2020
Close #5153

Description:

How do you solve it?

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

  • Unit test(positive and negative cases)
  • Function test
  • Performance test
  • N/A

Affects:

  • Documentation affected (Please add the label if documentation needs to be modified.)
  • Incompatibility (If it breaks the compatibility, please describe it and add the label.)
  • If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
  • Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

@xtcyclist xtcyclist requested a review from a team as a code owner December 29, 2022 03:48
@xtcyclist
Copy link
Contributor Author

This PR depends on #5149.

@xtcyclist xtcyclist changed the title Fix some bad type Fix the bad type evaluated from AttributeExpression on vertices Dec 29, 2022
@xtcyclist xtcyclist marked this pull request as draft December 29, 2022 05:04
@xtcyclist xtcyclist marked this pull request as ready for review December 29, 2022 08:38
@xtcyclist xtcyclist added ready-for-testing PR: ready for the CI test priority/hi-pri Priority: high ready for review labels Dec 29, 2022
Comment on lines +102 to +105
if (lvalue.isNull() && lvalue.getNull() == NullType::UNKNOWN_PROP) {
// return UNKNOWN_PROP as plain null values, instead of bad type.
return Value::kNullValue;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to modify the behivor of isNull.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using existing methods of Value for now.

@xtcyclist xtcyclist merged commit 9371098 into vesoft-inc:master Dec 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/hi-pri Priority: high ready for review ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected query error
7 participants