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

Implement query graph pruning #67

Closed
msm-code opened this issue Apr 15, 2020 · 1 comment · Fixed by #73
Closed

Implement query graph pruning #67

msm-code opened this issue Apr 15, 2020 · 1 comment · Fixed by #73
Assignees
Labels
level:medium This issue is of average difficulty priority:high Priority: high type:feature New feature zone:performance Making the database faster
Milestone

Comments

@msm-code
Copy link
Contributor

Ignore query graph paths that are "too branched".

Intuitively, When we have something like {AA BB CC DD ?? ?? ?? ?? ?? ?? EE FF GG HH} we should just split this into {AA BB CC DD} & {EE FF GG HH}.

Implementation-wise, compute branching level (using ngram density estimation) for every node, and collapse nodes where it's too big.

This is a blocking issue for releasing query graphs, because without it some queries will not be stable enough.

@msm-code msm-code added level:medium This issue is of average difficulty priority:high Priority: high zone:performance Making the database faster type:feature New feature labels Apr 15, 2020
@msm-code msm-code self-assigned this Apr 15, 2020
@msm-code msm-code added this to the v1.4.0 milestone Apr 15, 2020
@msm-code msm-code linked a pull request Apr 17, 2020 that will close this issue
@msm-code
Copy link
Contributor Author

Temporarily solved with #73

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level:medium This issue is of average difficulty priority:high Priority: high type:feature New feature zone:performance Making the database faster
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant