Closed achantavy closed 4 years ago
Just to add another data point, please see this post: https://community.neo4j.com/t/really-weird-query-not-returning-expected-data-after-upgrade-from-3-5-16-community-to-3-5-19-enterprise/21672/15?u=alexchantavy
Could this issue be related to full text indexing or something? Anyway, hope I'm not sending over a red herring, but thought it was worth noting the difference.
Hello @achantavy, I've looked into this a bit and think it's a browser/javascript-driver bug. Could you try running the queries via cypher-shell?
Hi @OliviaYtterbrink, wow you're right, the query works in cypher-shell but not in the browser!
neo4j> match(n:AWSTag{key:"aws:autoscaling:groupName"}) return n.key, n.value limit 50;
+------------------------------------------------------------+
| n.key | n.value |
+------------------------------------------------------------+
| "aws:autoscaling:groupName" | "{value1}-staging" |
| "aws:autoscaling:groupName" | "{value2}-production" |
| "aws:autoscaling:groupName" | "{value3}-production" |
| "aws:autoscaling:groupName" | "{value4}" |
| "aws:autoscaling:groupName" | "{value5}-production" |
| "aws:autoscaling:groupName" | "{value6}" |
... etc ...
Hi, is there any update on this? We're still seeing inconsistent query behavior on the web interface vs via cypher-shell.
Thanks for the detailed report and sorry about the delay. I've got time to look into this next week, so I'll have a new update some time next week
I looked into this just now and found the reason for the odd behaviour. We allow cypher queries to be prefixed with :auto
for automatic transactions, the current implementation simplly removes all instances of :auto
in the query. I'll fix it today, thanks again for your detailed report!
Hi there, I observed some unexpected query behaviors. Please see this forum thread for full context.
3.5.19 Enterprise
Ubuntu 14.04.6 LTS
The script that fills my DB uses 1.7.6 of the Python driver
Description
I recently upgraded my DB from 3.5.16 community to 3.5.19 with the following procedure:
service stop neo4j
apt-get install neo4j-enterprise=3.5.19
service start neo4j
This query works as expected:
as it returns a list of nodes with n.key = aws:autoscaling:groupName:
However when I just add an "s" to the key filter by running
I get 0 results:
I have a second neo4j server that was also upgraded using the same steps, running similar data and it shows this exact problem as well.
Things I've tried:
I have tried deleting all indexes on this :AWSTag node but that didn't work.
I then tried turning off the server, deleting /var/lib/neo4j/data/databases/graph.db/schema/*, and turning it on again. All other queries except for those related to
:AWSTags
work as expected (I think).PROFILE of the successful query:
PROFILE of the failing query:
Here are some other observations.
Observation 1
Expected behavior
should return a table that looks like
Actual behavior
The above query returns zero results.
Observation 2
Expected
should return only keys that actually start with "aws:auto".
Actual
The above query has these results:
Observation 3
Expected
If I do an exact field search like
I should get back nodes with
key='aws:autoscaling:groupName
, as shown in the "Description" above.Actual
I get no results.
Additional information
Partial output of
CALL db.stats.retrieve("GRAPH COUNTS")