fix subgraph step #4776
Merged
fix subgraph step #4776
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nevermore3
added
type/bug
nevermore3
force-pushed
the
fix_subgraph_loop_condition
branch
from
833e12f
to
584e3f2
Compare
nevermore3
force-pushed
the
fix_subgraph_loop_condition
branch
from
dc4ec82
to
61ff5c3
Compare
jievince
approved these changes
Oct 25, 2022
|
Could you explain this bug? |
In the case of only output vertex, also need to take one more step, because the attributes of the destination point need to be obtained by getneighbor in the second step. |
Shylock-Hg
approved these changes
Oct 25, 2022
Sophie-Xie
pushed a commit
that referenced
this pull request
Oct 25, 2022
* fix subgraph step * forbid function call in where clause * fix error
Shinji-IkariG
pushed a commit
that referenced
this pull request
Oct 25, 2022
* Fix/find start error (#4771) * Fix find start error. * Fix test. Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com> * Introduce JSON_EXTRACT function (#4743) * Introduce JSON_EXTRACT function close: #3513 Note, we don't support the path argument in this phase * address jievince's review commit removed the unecessary interface of construct Map from Value * Type handling Only primitive types are supported * Support depth1 nested * lint: fmt * ut: ctest, fixed wrong expression of Map * fix ut errors * tck: case for json_extract added Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com> * Fix bug #1337 from ent (#4740) * Return an semantic error if no tag is found for a property while validating a match. * Return an semantic error if no tag is found for a property while validating a match. * Add a tck case for the fixed bug. * commented out unused codes. * add tag in tck cases * fixing tck * updated tck cases to add missing cases that are supposed to be there. * Return an semantic error if no tag is found for a property while validating a match. * Add a tck case for the fixed bug. * commented out unused codes. * add tag in tck cases * fixing tck * updated tck cases to add missing cases that are supposed to be there. * update * update tck case. Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com> * Fix RollUpApplyExecutor (#4778) Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com> * Fix mutil-match crash in optimization phase (#4780) fmt small fix small fix * fix subgraph step (#4776) * fix subgraph step * forbid function call in where clause * fix error Co-authored-by: shylock <33566796+Shylock-Hg@users.noreply.github.com> Co-authored-by: Wey Gu <weyl.gu@gmail.com> Co-authored-by: Cheng Xuntao <7731943+xtcyclist@users.noreply.github.com> Co-authored-by: Yichen Wang <18348405+Aiee@users.noreply.github.com> Co-authored-by: kyle.cao <kyle.cao@vesoft.com> Co-authored-by: jimingquan <mingquan.ji@vesoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
close #4770
#4764
Description:
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:
Checklist:
Tests:
Affects:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: