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

More lookup TCK tests #5218

Merged
merged 14 commits into from
Jan 30, 2023
Merged

More lookup TCK tests #5218

merged 14 commits into from
Jan 30, 2023

Conversation

yixinglu
Copy link
Contributor

@yixinglu yixinglu commented Jan 6, 2023

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

vesoft-inc/nebula-ent#1754

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 .....

@yixinglu yixinglu marked this pull request as ready for review January 30, 2023 03:49
@yixinglu yixinglu added the ready-for-testing PR: ready for the CI test label Jan 30, 2023
@yixinglu yixinglu changed the title More lookup TCK tests on ngdata More lookup TCK tests Jan 30, 2023
# (TODO) Unsupported cases due to the lack of float precision
When executing query:
"""
LOOKUP ON weight WHERE weight.WEIGHT > 70.5 YIELD id(vertex) as name;
Copy link
Contributor

Choose a reason for hiding this comment

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

YIELD weight.WEIGHT for more intuitive validation. Any issue related to float precision here?

@@ -133,3 +133,55 @@ Feature: Push Limit down IndexScan Rule
| 7 | Limit | 8 | |
| 8 | EdgeIndexPrefixScan | 9 | {"limit": "3"} |
| 9 | Start | | |

Scenario: some variables in where clause of lookup statement
Copy link
Contributor

@czpmango czpmango Jan 30, 2023

Choose a reason for hiding this comment

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

Add some test cases related to cypher variable:

UNWIND ["A", "B"] AS name | LOOKUP ON player  WHERE player.name starts with $-.name YIELD id(vertex) as id;
UNWIND ["A", "B"] AS name | LOOKUP ON player  YIELD id(vertex) as id;

@Sophie-Xie Sophie-Xie merged commit 88a93c4 into vesoft-inc:master Jan 30, 2023
@yixinglu yixinglu deleted the lookup-test branch January 30, 2023 09:51
Sophie-Xie added a commit that referenced this pull request Feb 2, 2023
* More lookup tests on ngdata

* Test edge property of double and geography types

* Restore geography test for lookup

* comment back tests

* More lookup test cases

* restore ngdata tests

* drop the used space

* Fix failed

* refine step

* some variables in where clause of lookup statement

* some variabes in yield clause of lookup statement

* More yield variable test

---------

Co-authored-by: Sophie <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-v3.4 ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants