Moved ClusterParser exceptions to BaseParser class #3475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request check-list
Please make sure to review and check all of these items:
NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
If RESP3 is enabled, the ClusterParser becomes immediately overridden with _RESP3Parser which leads to the fact that all additional exceptions isn't handled by cluster implementation.
ClusterParser class shouldn't exist and inherit other parsers just to extend a list of exceptions that should be associated with given error codes. Parsing errors and associate them to exception classes is a responsibility of parsers itself regardless of server topology, potentially you could get any error code as a response from server and parser should be aware of it.