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

enhance same attribute name for different tags #3255

Merged
merged 16 commits into from
Dec 29, 2021

Conversation

nevermore3
Copy link
Contributor

@nevermore3 nevermore3 commented Nov 2, 2021

What type of PR is this?

feature

Which issue(s) this PR fixes:

close #xxx

What this PR does / why we need it?

Add tag information when getting the attributes of the vertex,

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

Additional context:

Checklist:

  • Documentation affected (If need to modify document, please label it.)
  • Incompatible (If it is incompatile, please describle it and label it.)
  • Need to cherry pick (If need to cherry pick to some branchs, please label the destination version(s).)
  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory

Release notes:

Please confirm whether to reflect in release notes and how to describe:

                                                            `

@nevermore3 nevermore3 added do not review PR: not ready for the code review yet wip Solution: work in progress and removed do not review PR: not ready for the code review yet labels Nov 2, 2021
@nevermore3 nevermore3 added this to the v3.0.0 milestone Nov 2, 2021
@nevermore3 nevermore3 force-pushed the add_LabelTagAttributeExpression branch 4 times, most recently from fa692a9 to c68a152 Compare November 11, 2021 12:30
@nevermore3 nevermore3 changed the title add labeltagpropexpression enhance same attribute name for different tags Nov 11, 2021
@nevermore3 nevermore3 added ready-for-testing PR: ready for the CI test and removed wip Solution: work in progress labels Nov 11, 2021
@Aiee Aiee added the doc affected PR: improvements or additions to documentation label Nov 12, 2021
@codecov-commenter
Copy link

codecov-commenter commented Nov 12, 2021

Codecov Report

Merging #3255 (da6edb0) into master (99f1f7a) will increase coverage by 0.00%.
The diff coverage is 82.06%.

Impacted file tree graph

@@           Coverage Diff            @@
##           master    #3255    +/-   ##
========================================
  Coverage   85.19%   85.20%            
========================================
  Files        1304     1306     +2     
  Lines      121308   122289   +981     
========================================
+ Hits       103352   104200   +848     
- Misses      17956    18089   +133     
Impacted Files Coverage Δ
src/clients/storage/StorageClient.h 100.00% <ø> (ø)
src/clients/storage/StorageClientBase-inl.h 74.47% <ø> (+1.79%) ⬆️
src/codec/RowWriterV2.h 94.44% <ø> (ø)
src/common/datatypes/Value.h 97.87% <ø> (ø)
src/common/expression/ExprVisitor.h 100.00% <ø> (ø)
src/common/expression/Expression.h 100.00% <ø> (ø)
src/common/time/TimeConversion.h 100.00% <ø> (ø)
src/common/utils/IndexKeyUtils.h 90.93% <0.00%> (ø)
src/graph/optimizer/rule/IndexScanRule.h 100.00% <ø> (ø)
...graph/optimizer/rule/PushFilterDownProjectRule.cpp 98.80% <ø> (ø)
... and 102 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af74bab...da6edb0. Read the comment docs.

| [[:like "wang"->"zhang" @0 {likeness: 91}]] |
When executing query:
"""
match p= (v:player)-[e:like]->(d) where v.student.age > 19 return v.student.score, v.student.name, v.player.name
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we support v{.player.name, .student.name}?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

not support right now

Copy link
Contributor

Choose a reason for hiding this comment

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

v.{player.name, student.name}
v{.player.name, .student.name}

Copy link
Contributor

Choose a reason for hiding this comment

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

[e:like:serve]

@nevermore3 nevermore3 added do not review PR: not ready for the code review yet wip Solution: work in progress and removed ready-for-testing PR: ready for the CI test labels Dec 2, 2021
@nevermore3 nevermore3 force-pushed the add_LabelTagAttributeExpression branch 4 times, most recently from 0b13e85 to 18d4149 Compare December 6, 2021 09:02
@nevermore3 nevermore3 added ready-for-testing PR: ready for the CI test and removed do not review PR: not ready for the code review yet wip Solution: work in progress labels Dec 6, 2021
@nevermore3 nevermore3 force-pushed the add_LabelTagAttributeExpression branch 2 times, most recently from 3923a3b to 0f5d679 Compare December 6, 2021 09:06
Copy link
Contributor

@yixinglu yixinglu left a comment

Choose a reason for hiding this comment

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

Need to test the previous usage of var.prop is illegal.

tests/tck/features/match/Base.feature Outdated Show resolved Hide resolved
CPWstatic
CPWstatic previously approved these changes Dec 28, 2021
Copy link
Contributor

@CPWstatic CPWstatic left a comment

Choose a reason for hiding this comment

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

LGTM. But there are a lot conflicts with another pr which implements the openCypher.

@nevermore3 nevermore3 force-pushed the add_LabelTagAttributeExpression branch from ec492a5 to e8065cd Compare December 29, 2021 04:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc affected PR: improvements or additions to documentation 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.

There is no way to implement a tag query as a function
8 participants