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
Failing to read correct cypher schema from neo4j #666
Comments
Thanks for reporting this. However, this bug doesn't seem to be the same as reported in neo4j/neo4j#9726. The procedure that you are using (i.e. In CAPS, we require to know all data types a property might have, e.g. String, Integer, in order to correctly compute the resulting Spark column type.That's also why we cannot use the APOC procedure as it does not report conflicting property types. I'll try to reproduce the issue and get back to you. |
We tried the following steps to reproduce the behaviour for nodes:
We tried the following steps to reproduce the behaviour for relationships:
Could you please report the steps you took to produce the error? Thanks. |
Thanks for your answer, I found that property "Auscultation" was not deleted and that's why this error is produced. Thanks for your contribution. |
Glad to hear that, thanks for reporting the success. |
Hi,
When I try to read from my neo4j server by using below command:
val names = graph.cypher("MATCH(n:Disease) RETURN n.name AS name")
this error is raised:
This error shows that there is a property named "Auscultation" which has conflict with another property named "auscultation".
So I checked the cypher properties schema with this command:
CALL org.opencypher.okapi.procedures.schema
And this is the result related to property "Auscultation":
But the point is that there is not any "Auscultation" property and I've removed it before but neo4j thinks that it still exists.
This Neo4j bug has been issued in neo4j_issue#9726
This is solved by reading procedure from Apoc plugin not from neo4j built-in schema.
So I think CAPS needs to read schema correctly not from neo4j built-in method to not hit this kind of bug anymore.
The text was updated successfully, but these errors were encountered: