You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2019. It is now read-only.
+-----------+
| COUNT(nd) |
+-----------+
| 59 |
+-----------+
1 row
Properties set: 59
1611 ms
The indexes don't work after you start the actual neo4j server.
When you start the neo4j server and run this query once again without the -path:
$ ./bin/neo4j-shell -config /var/lib/neo4j/conf/neo4j-server.properties -file autoindex.neo4jshell
indexes work fine and the data is correct.
here are the messages.log:
noserver
server
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
# Auto-indexing
# Enable auto-indexing for nodes, default is false
node_auto_indexing=true
# The node property keys to be auto-indexed, if enabled
node_keys_indexable=text
@jexp well, it looks like these options were deprecated. but how do they relate to the behavior I described in the first message? why indexes don't work when you create them in "single" (without actual neo4j server start) mode?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When you run the following query:
using neo4j-shell with
-path
parameter (and stopped main neo4j server):The indexes don't work after you start the actual neo4j server.
When you start the neo4j server and run this query once again without the
-path
:indexes work fine and the data is correct.
here are the
messages.log
:noserver
server
The text was updated successfully, but these errors were encountered: