Skip to content

Commit ade2c39

Browse files
committed
Fix doc formatting: JSON schema initialization flow CTR
Signed-off-by: Oleksandr Porunov <alexandr.porunov@gmail.com>
1 parent 66fdcc7 commit ade2c39

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/schema/schema-init-strategies.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -405,9 +405,9 @@ Following the rules above (defined in `JSON Schema Format`) an example of JSON s
405405
Currently, JSON schema initialization flow is simple and doesn't include any schema update or schema migration features.
406406
The flow is split on multiple phases:
407407

408-
1) Creation of simple elements: `PropertyKey`, `VertexLabel`, `EdgeLabel`.
409-
2) Creation of indices: Composite indexes, Vertex-centric Edge indexes, Vertex-centric Property indexes, Mixed indexes.
410-
3) Indexes activation phase (configured via `schema.init.json.indices-activation`).
408+
1. Creation of simple elements: `PropertyKey`, `VertexLabel`, `EdgeLabel`.
409+
2. Creation of indices: Composite indexes, Vertex-centric Edge indexes, Vertex-centric Property indexes, Mixed indexes.
410+
3. Indexes activation phase (configured via `schema.init.json.indices-activation`).
411411

412412
!!! note
413413
Current implementation of JSON schema importer only creates elements, but it never updates them even if you change

0 commit comments

Comments
 (0)