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

Filter push down don't work in Go sentence #4838

Closed
Shylock-Hg opened this issue Nov 9, 2022 · 1 comment · Fixed by #4841
Closed

Filter push down don't work in Go sentence #4838

Shylock-Hg opened this issue Nov 9, 2022 · 1 comment · Fixed by #4841
Assignees
Labels
priority/hi-pri Priority: high severity/minor Severity of bug type/bug/functionality Bugs preventing the database to deliver a promised function. type/bug Type: something is unexpected
Milestone

Comments

@Shylock-Hg
Copy link
Contributor

Shylock-Hg commented Nov 9, 2022

Please check the FAQ documentation before raising an issue

Describe the bug (required)

GO FROM "{ego_id}" OVER communication WHERE communication._dst NOT IN \
{two_hop_list} \
YIELD communication._dst as correspondence_id, communication.snap_send as strength | \
ORDER BY $-.strength DESC | LIMIT {MAX_ONE_HOP_COUNT} | \
GO FROM $-.correspondence_id OVER communication REVERSELY WHERE communication._dst IN \
{two_hop_list} \
YIELD communication._dst AS E, $-.correspondence_id | GROUP BY $-.E YIELD $-.E as candidate, count(*) as mutual_communication_friend_count;

The second GO sentence don't push down filter as expected.

Your Environments (required)

  • OS: uname -a
  • Compiler: g++ --version or clang++ --version
  • CPU: lscpu
  • Commit id (e.g. a3ffc7d8) v3.3.0 community version

How To Reproduce(required)

Steps to reproduce the behavior:

  1. Step 1
  2. Step 2
  3. Step 3

Expected behavior

Additional context

@Shylock-Hg Shylock-Hg added the type/bug Type: something is unexpected label Nov 9, 2022
@Sophie-Xie Sophie-Xie added this to the v3.4.0 milestone Nov 9, 2022
@Shylock-Hg Shylock-Hg self-assigned this Nov 9, 2022
@wey-gu
Copy link
Contributor

wey-gu commented Nov 9, 2022

Attached a handy query to reproduce, thanks @Shylock-Hg :)!

GO FROM "player101" OVER follow WHERE follow._dst NOT IN ["player109", "player113", "player108"] AND follow.degree > 5 YIELD follow._dst as correspondence_id, follow.degree as degree | ORDER BY $-.degree DESC | LIMIT 20 |
GO FROM $-.correspondence_id OVER follow REVERSELY WHERE follow._dst IN ["player109", "player113", "player108"] AND follow.degree > 5 YIELD follow._dst AS E, $-.correspondence_id |  GROUP BY $-.E YIELD $-.E, count(*);

@xtcyclist xtcyclist added the type/bug/functionality Bugs preventing the database to deliver a promised function. label Nov 9, 2022
@Sophie-Xie Sophie-Xie added the priority/hi-pri Priority: high label Nov 9, 2022
@jinyingsunny jinyingsunny added the severity/minor Severity of bug label Nov 10, 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 severity/minor Severity of bug type/bug/functionality Bugs preventing the database to deliver a promised function. type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants