-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can query a node from index #179
Comments
You're passing |
The other thing is, you're not seeing if you're getting any errors. For each of the callbacks, it's good to check |
For sure. This code is only to point out the flow. console.log is sufficient to see that there is an empty response which is the point of this demonstration. |
Got it. Would you mind confirming a couple things for sanity:
Assuming both of these are indeed the case:
|
no errors. yes I use node.index. I can't get the node from the index even after a long delay. Not a eventual consistency case. |
question: have you tried doing this yourself? |
Okay, surprising. No, I haven't tried this myself. We use exclusively v2 schema indexes and legacy auto-indexes, not legacy manual indexes. I can try myself later. Another thing to try would be using the Neo4j webadmin to do these things manually. Does it work there? If so, suggests a node-neo4j or code bug. If not, suggests a Neo4j bug. |
However, we do cover manual indexing in our tests, and that's always worked: Lines 220 to 224 in b1f6348
|
What happens here?
var indexName = 'myNodeIndex';
var node = db.createNode({name: 'hey'});
node.save(function() {
db.index(indexName, 'name', 'hey', function() {
db.getIndexedNode(indexName, 'name', 'hey', console.log)
})
})
Expected:
getIndexedNode returns the node that just got indexed.
Actual:
getIndexedNode has empty response
The text was updated successfully, but these errors were encountered: