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.

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

Update headings #157

Merged
merged 5 commits into from
Jul 18, 2024
Merged

Update headings #157

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
475acc6
Update headings
NataliaIvakina Jul 17, 2024
2c87da3
Update all-notifications.adoc
NataliaIvakina Jul 17, 2024
33a7081
Merge branch 'gql-notifications' into new-headings
NataliaIvakina Jul 18, 2024
2eb68a8
Update modules/ROOT/pages/notifications/all-notifications.adoc
NataliaIvakina Jul 18, 2024
58ef72a
Update all-notifications.adoc
NataliaIvakina Jul 18, 2024
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
59 changes: 29 additions & 30 deletions modules/ROOT/pages/notifications/all-notifications.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ The following page provides an overview of all notifications in Neo4j, along wit
Performance notifications are returned whenever the query uses costly operations and the performance may be improved by changing the query or adding an index.

[#_neo_clientnotification_statement_cartesianproduct]
=== CartesianProduct
=== Cartesian product

This notification is returned when there is a Cartesian product in the plan.

Expand Down Expand Up @@ -113,7 +113,7 @@ MATCH (c:Child)-[:ChildOf]->(p:Parent) RETURN c, p
=====

[#_neo_clientnotification_statement_unboundedvariablelengthpattern]
=== UnboundedVariableLengthPattern
=== Unbounded variable length pattern

This notification is returned when there is no upper bound specified on the variable length relationship.

Expand Down Expand Up @@ -198,7 +198,7 @@ MATCH p=shortestPath((n)-[*..8]->(m)) RETURN p
=====

[#_neo_clientnotification_statement_exhaustiveshortestpath]
=== ExhaustiveShortestPath
=== Exhaustive shortest path

This notification is returned when a predicate, given on the shortest path, needs to inspect the whole path before deciding whether it is valid, the shortest path might fall back to the exhaustive search algorithm.
For more information, see link:https://neo4j.com/docs/cypher-manual/current/execution-plans/shortestpath-planning#_shortest_pathadditional_predicate_checks_on_the_paths[Cypher manual -> Shortest path - additional predicate checks on the paths].
Expand Down Expand Up @@ -290,7 +290,7 @@ RETURN p
=====

[#_neo_clientnotification_statement_noapplicableindex]
=== NoApplicableIndex
=== No applicable index

This notification is returned when using `LOAD CSV` with a `MATCH` or a `MERGE` clause that matches a non-indexed label.
This may not perform well on large data sets.
Expand Down Expand Up @@ -375,7 +375,7 @@ CREATE INDEX FOR (n:Person) ON (n.name)
=====

[#_neo_clientnotification_statement_eageroperator]
=== EagerOperator
=== Eager operator

This notification is returned when the execution plan for a query contains the `Eager` operator.

Expand Down Expand Up @@ -473,7 +473,7 @@ RETURN line


[#_neo_clientnotification_statement_dynamicproperty]
=== DynamicProperty
=== Dynamic property

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -616,7 +616,7 @@ MATCH ()-[r: KNOWS]->() WHERE r.since IS NOT NULL RETURN r
=====

[#_neo_clientnotification_statement_codegenerationfailed]
=== CodeGenerationFailed
=== Unsupported runtime - CodeGenerationFailed
NataliaIvakina marked this conversation as resolved.
Show resolved Hide resolved

The `CodeGenerationFailed` notification is created when it is not possible to generate a code for a query, for example, when the query is too big.
For more information about the specific query, see the stack trace in the _debug.log_ file.
Expand Down Expand Up @@ -654,7 +654,7 @@ This behavior of the Cypher planner or runtime can be changed by setting the con
In this case, the query will return an error.

[#_neo_clientnotification_statement_joinhintunfulfillablewarning]
=== JoinHintUnfulfillableWarning
=== Join hint unfulfillable

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -739,7 +739,7 @@ The only option for this query is to either remove the hint or modify the query


[#_neo_clientnotification_schema_hintedindexnotfound]
=== HintedIndexNotFound
=== Hinted index not found

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -869,7 +869,7 @@ If the spelling is correct, either create the index or remove the hint from the
Unrecognized notifications are returned when the query or command mentions entities that are unknown to the system.

[#_neo_clientnotification_database_homedatabasenotfound]
=== HomeDatabaseNotFound
=== Home database not found

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -940,7 +940,7 @@ Verify that the home database name is not misspelled.
=====

[#_neo_clientnotification_statement_unknownlabelwarning]
=== UnknownLabelWarning
=== Unknown label

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -1011,7 +1011,7 @@ If you plan to create nodes with that label in the future, no change is needed.
=====

[#_neo_clientnotification_statement_unknownrelationshiptypewarning]
=== UnknownRelationshipTypeWarning
=== Unknown relationship type

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -1082,7 +1082,7 @@ If you plan to create relationships of this type in the future, no change is nee
=====

[#_neo_clientnotification_statement_unknownpropertykeywarning]
=== UnknownPropertyKeyWarning
=== Unknown property key

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -1160,7 +1160,7 @@ If you plan to create that property key in the future, no change is needed.
Unsupported notifications are returned when the query or command is trying to use features that are not supported by the current system or using experimental features that should not be used in production.

[#_neo_clientnotification_statement_runtimeunsupportedwarning]
=== RuntimeUnsupportedWarning
=== Unsupported runtime

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -1241,7 +1241,7 @@ SHOW INDEXES YIELD *

[role=label--deprecated-5.14]
[#_neo_clientnotification_statement_runtimeexperimental]
=== RuntimeExperimental
=== RuntimeExperimental
NataliaIvakina marked this conversation as resolved.
Show resolved Hide resolved

[NOTE]
====
Expand Down Expand Up @@ -2048,8 +2048,8 @@ m|DEPRECATION
m|WARNING
|===

[#_neo_clientnotification_request_deprecatedformat]
=== DeprecatedFormat
[#_neo_clientnotification_request_]
=== Feature deprecated with replacement - DeprecatedFormat

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -2290,7 +2290,7 @@ Verify that this is the intended privilege and role.
=====

[#_neo_clientnotification_security_impossiblerevokecommand]
=== ImpossibleRevokeCommand
=== Impossible revoke command

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -2700,6 +2700,7 @@ Topology notifications provide additional information related to managing databa
[#_neo_clientnotification_cluster_serveralreadyenabled]
=== ServerAlreadyEnabled
NataliaIvakina marked this conversation as resolved.
Show resolved Hide resolved


.Notification details
[cols="<1s,<4"]
|===
Expand Down Expand Up @@ -2830,7 +2831,7 @@ Verify that this is the intended server.
=====

[#_neo_clientnotification_cluster_nodatabasesreallocated]
=== NoDatabasesReallocated
=== No databases reallocated

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -2907,12 +2908,11 @@ For example, when there are three servers, each hosting databases `foo` and `bar
**Scenario 2:** The cluster appears unbalanced, but server constraints prevent you from moving to a better, more balanced, allocation.
For example, assuming server 1 hosts databases `foo` and `bar`, server 2 hosts only `foo`, and server 3 hosts no databases.
Then, a better allocation would move `foo` from server 1 to server 3, but if server 3 has the constraint `deniedDatabases:['foo']}`, then the cluster is already balanced subject to this constraint.

======
=====

[#_neo_clientnotification_cluster_cordonedserversexistedduringallocation]
=== CordonedServersExistedDuringAllocation
=== Cordoned servers existed during allocation

This notification is returned when a Cypher administration command triggers an allocation decision and some of the servers are cordoned.
For example, `CREATE DATABASE`, `ALTER DATABASE`, `DEALLOCATE DATABASES FROM SERVER[S]`, and `ALTER DATABASE` return this notification. However, `REALLOCATE DATABASES` requires that there are no cordoned servers and, therefore, does not return it.
Expand Down Expand Up @@ -2977,13 +2977,12 @@ note: successful completion - cordoned servers existed during allocation.
Cordoned servers existed when making an allocation decision.
Server(s) `123e4567-e89b-12d3-a456-426614174000` are cordoned.
This can impact allocation decisions.

======
=====


[#_neo_clientnotification_cluster_requestedtopologymatchedcurrenttopology]
=== RequestedTopologyMatchedCurrentTopology
=== Requested topology matched current topology

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -3056,7 +3055,7 @@ No allocations were changed.
Schema notifications provide additional information related to indexes and constraints.

[#_neo_clientnotification_schema_indexorconstraintalreadyexists]
=== IndexOrConstraintAlreadyExists
=== Index or constraint already exists

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -3289,7 +3288,7 @@ CREATE CONSTRAINT myConstraint2 IF NOT EXISTS FOR (n:Label2) REQUIRE (n.property
=====

[#_neo_clientnotification_schema_indexorconstraintdoesnotexist]
=== IndexOrConstraintDoesNotExist
=== Index or constraint does not exist

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -3410,7 +3409,7 @@ Verify that this is the intended constraint and that it is spelled correctly.
`GENERIC` notification codes do not belong to any wider category and do not have any connection to each other.

[#_neo_clientnotification_statement_subqueryvariableshadowing]
=== SubqueryVariableShadowing
=== Subquery variable shadowing

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -3512,7 +3511,7 @@ RETURN *
=====

[#_neo_clientnotification_statement_parameternotprovided]
=== ParameterNotProvided
=== Parameter missing

.Notification details
[cols="<1s,<4"]
Expand Down Expand Up @@ -3585,7 +3584,7 @@ Provide the parameter to be able to cache the plan.


[#_neo_clientnotification_procedure_procedurewarning]
=== ProcedureWarning
=== Procedure or function execution warning

.Notification details
[cols="<1s,<4"]
Expand All @@ -3612,7 +3611,7 @@ m|WARNING

[role=label--new-5.4]
[#_neo_clientnotification_statement_unsatisfiablerelationshiptypeexpression]
=== UnsatisfiableRelationshipTypeExpression
=== Unsatisfiable relationship type expression

When matching on a relationship type expression that can never be satisfied, for example asking for zero, more than one or contradictory types.

Expand Down Expand Up @@ -3673,7 +3672,7 @@ The expression `R1&R2` cannot be satisfied because relationships must have exact

[role=label--new-5.5]
[#_neo_clientnotification_statement_repeatedrelationshipreference]
=== RepeatedRelationshipReference
=== Repeated relationship reference

.Notification category details
[cols="<1s,<4"]
Expand Down