Using Indexes in Neo4j
Module overview
Indexes are used to provide faster Full definition for Cypher (opens in a new tab)Neo4j's implementation of GQL, the ISO standard query language for graph databases. It is declarative: you describe the pattern to find, and the database decides how to find it. queries. You have already learned that uniqueness Full definition for constraint (opens in a new tab)A rule the database enforces on every node or relationship with a given label or type, rejecting any write that breaks it. enable you to quickly look up a Full definition for node (opens in a new tab)A vertex in a graph. In a property graph it can carry labels and properties.. This is because a uniqueness constraint is implemented as an index. You can also use indexes to make queries faster, even when multiple nodes or Full definition for relationship (opens in a new tab)A named, directed connection between two nodes. Every relationship has a type, a start node and an end node. have the same Full definition for property (opens in a new tab)A named value stored on a node or a relationship. value.
In this module, you will:
- Learn about the types indexes available in Neo4j and why you would use them.
- Create an index on a node property.
- Create an index on a relationship property.
- Create a composite index on a set of node properties.
- Create a TEXT index.
- Manage indexes in the graph.
Resources
During this course, you can refer to: