I'm actually creating a node entity in the blueprint datastore, this way :
I'm creating 3 unique indexed property, but, when I start the server for the first time, there are no indexes created for those properties. By reading the memgraph documentation, it doesn't works the same way as neo4j (which creates automatically the index on a unique constraint)
To corroborate what the documentation is saying, I ran a Read Query integration test with 66.000 nodes in the database. With the constraint without index, the test takes 30ms. With the constraint and the manually created index, the test takes 6ms.
Expected Behavior
When the server is started, the database should contain an index for each of my unique constraint
Kind of issue
In which operating systems have you tested?
Hello !
I'm actually creating a node entity in the blueprint datastore, this way :
I'm creating 3 unique indexed property, but, when I start the server for the first time, there are no indexes created for those properties. By reading the memgraph documentation, it doesn't works the same way as neo4j (which creates automatically the index on a unique constraint)
To corroborate what the documentation is saying, I ran a Read Query integration test with 66.000 nodes in the database. With the constraint without index, the test takes 30ms. With the constraint and the manually created index, the test takes 6ms.
Expected Behavior
When the server is started, the database should contain an index for each of my unique constraint