executeQuery not throwing errors
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
We have a need to use the executeQuery method to do large data import as our cypher queries are complicated (such as load csv). However, we are not seeing the errors this method is throwing (if there are any neo4j driver errors while executing the cypher query) and it looks like the errors are being caught and a null result is returned. Is there any way to retrieve the errors, if any, that are thrown by executeQuery?
Contributor guide
Research direction
Locate the executeQuery entry point and trace how Neo4j driver errors are handled during cypher execution. Reproduce the large-import case with a failing query, then verify that callers can retrieve the execution error instead of receiving only a null result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, neo4j
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100