Database Reference
In-Depth Information
Writing data in a schema
Neo4j 2.0 introduces the schema for managing the indexes and constraints. Legacy indexes
are still supported but are deprecated and would be removed from the later versions of
Neo4j. The rationale behind schema was to provide an API that leverages indexes as soon
as they are defined by the users. The objective was to have an automatic process for insert-
ing/updating and searching the indexes without any manual intervention. At the time of
writing this topic, Neo4j Version 2.1.5 was released and APIs in schema were available to
provide core features of indexes but still there were some features such as full-text searches
case-insensitive searches, or spatial searches that are still in development and are due to be
released in the upcoming versions of Neo4j.
Let's see the usage of various APIs in the schema package for managing indexes using Java
and REST APIs.
