Skip to content

Add .retriable to the Neo4jError #901

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

Merged
merged 2 commits into from
Mar 21, 2022
Merged

Conversation

bigmontz
Copy link
Contributor

@bigmontz bigmontz commented Mar 16, 2022

This property should helps users to implement custom retries logics.

Along with the property, the static function Neo4jError.isRetriable(error) and
the function isRetriableError(error) were added for saving boilerplates and avoid
the error type checking to be spread across the client and driver code base.

The internal function canRetryOn(error) and the retry-strategy file were removed
since the logic implemented there was moved to the error module replaced by
the isRetriableError(error) usage.

This property should helps users to implement custom retries logics.

Along with the property, the static function `Neo4jError.isRetriable(error)` and
the function `isRetriableError(error)` were added for saving boilerplates and avoid
the error typechecking to be spread accross the client and driver code base.

The internal function `canRetryOn(error)` and the `retry-strategy` file were removed
since the logic implemented there was moved to the `error` module replaced by
the `isRetriableError(error)` usage.
@bigmontz bigmontz force-pushed the 5.0-retriable-errors branch from 634a0b1 to 0fc5145 Compare March 16, 2022 12:36
@bigmontz bigmontz merged commit 5bb4f85 into neo4j:5.0 Mar 21, 2022
@bigmontz bigmontz deleted the 5.0-retriable-errors branch March 21, 2022 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants