Index configuration - Operations Manual

How to configure indexes to enhance performance in search, and to enable full-text search.

Index configuration This page describes how to configure Neo4j indexes to enhance search performance and enable full-text search. The supported index types are: Range Point Text Full-text Token lookup All types of indexes can be created and dropped using Cypher and they can also all be used to index both nodes and relationships. The token lookup index is the only index present by default in the database. Range, point, text, and full-text indexes provide a mapping from a property value to an entity (node or relationship). Token lookup indexes are different and provide a mapping from labels to n

related reading

• Search-performance indexes - Cypher Manualneo4j.com
• Full-text index analyzer providers - Java Referenceneo4j.com
• Why graph indexing is importantcommunity.neo4j.com
• Indexing a string property is taking several days and it doesn't seem near to completion - Operations - Neo4j Online Communitycommunity.neo4j.com
• The vector database to build knowledgeable AI | Pineconepinecone.io
• Indexing a string property is taking several days and it doesn't seem near to completion - #8 by dsolow - Operations - Neo4j Online Communitycommunity.neo4j.com
• turbopufferturbopuffer.com
• Create an advanced search engine with PostgreSQL | xataxata.io
• Fast regex search: indexing text for agent tools · Cursorcursor.com
• Building a web search engine from scratch in two months with 3 billion neural embeddingsblog.wilsonl.in
• Full Text Search | Supabase Docssupabase.com
• How to Index Fields for Vector Search - MongoDB Vector Search - MongoDB Docsmongodb.com