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

Properly handle selectivities when many labels #5414

Merged
merged 1 commit into from Sep 24, 2015

Conversation

pontusmelke
Copy link
Contributor

Because of the independency assumption we could end up in situations with
label selectivities larger than 1.0, and completely blow up when having
many labels.

Fixes #5336

@systay
Copy link
Contributor

systay commented Sep 23, 2015

LGTM 👍

Because of the independency assumption we could end up in situations where
label selectivities was larger than 1.0, and completely blow up when having
many labels.

Fixes GH#5336
systay added a commit that referenced this pull request Sep 24, 2015
Properly handle selectivities when many labels
@systay systay merged commit 53ac064 into neo4j:2.2 Sep 24, 2015
@@ -133,12 +132,12 @@ case class PatternSelectivityCalculator(stats: GraphStatistics, combiner: Select

private def calculateLabelSelectivity(specs: Seq[TokenSpec[LabelId]]): Selectivity = {
val selectivities = specs map {
case SpecifiedButUnknown() => Selectivity(0)
case SpecifiedButUnknown() => Selectivity.ONE
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks weird. It went from Selectivity(0) to Selectivity.ONE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants