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
Please note that GitHub issues are only meant for bug reports/feature requests. If you have questions on how to use APOC, please ask on the Neo4j Discussion Forum instead of creating an issue here.
Feature description (Mandatory)
apoc.cypher.runTimeboxed terminates long running query and returns nothing, which makes it confusing as client wouldn't know whether the query find nothing or it's terminated.
Considered alternatives
Return a status code together with value. The status code should indicate:
query is complete
query is terminated
query failed due to syntax error
How this feature can improve the project?
Remove ambiguity and improve usability.
The text was updated successfully, but these errors were encountered:
Comment by tolomaus Saturday Sep 05, 2020 at 17:05 GMT
Looking at the implementation details, could it be that the procedure may return partial results, in case the transaction is terminated while adding the results one by one in the queue?
Any chance that the fix by @sarmbruster could be merged anytime soon?
There have been some updates here :) It will be released in an upcoming release! The changes adds a new config argument which gives the option to fail on error (so an exception is thrown by the proc if an exception is hit during the running or the timeout is hit) and an option to turn on a status update where the final row returned will give info on if the result set is complete or not :)
Issue by neo4j-apac
Friday Jun 21, 2019 at 13:03 GMT
Originally opened as neo4j-contrib/neo4j-apoc-procedures#1233
Guidelines
Please note that GitHub issues are only meant for bug reports/feature requests. If you have questions on how to use APOC, please ask on the Neo4j Discussion Forum instead of creating an issue here.
Feature description (Mandatory)
apoc.cypher.runTimeboxed terminates long running query and returns nothing, which makes it confusing as client wouldn't know whether the query find nothing or it's terminated.
Considered alternatives
Return a status code together with value. The status code should indicate:
How this feature can improve the project?
Remove ambiguity and improve usability.
The text was updated successfully, but these errors were encountered: