Skip to content

dbms.cypher.infer_schema_parts defaults to MOST_SELECTIVE_LABEL #2059

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

dbms.cypher.infer_schema_parts defaults to MOST_SELECTIVE_LABEL #2059

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/ROOT/pages/configuration/configuration-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1816,7 +1816,7 @@ If more than one label can be inferred for a given node, the planner keeps the m
|Valid values
a|One of [MOST_SELECTIVE_LABEL, OFF].
|Default value
m|+++OFF+++
m|+++MOST_SELECTIVE_LABEL+++
|===

For some queries, the planner can infer predicates such as labels or types from the graph structure that can improve estimating the number of rows that each operator produces.
Expand Down
Loading