-
Notifications
You must be signed in to change notification settings - Fork 46
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
[FEAT] [EXPERIMENTAL] direct get of messages for KV #316
Conversation
[FEAT] [KV] experimental - KvOptions can now specify `allow_direct` which enables the creation of streams on servers that supported that enable the direct api which may provide better performance on gets for KV. [FIX] internal checkJsErrorCode() was passing a status instead of a description, creating error descriptions prefixed by the error code
The matching server pull |
@@ -89,7 +89,7 @@ export function checkJsError(msg: Msg): NatsError | null { | |||
if (!h) { | |||
return null; | |||
} | |||
return checkJsErrorCode(h.code, h.status); | |||
return checkJsErrorCode(h.code, h.description); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We want to check description vs status?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the status line contains the code/message - the description is just the message part of that combo, so it uglified some of the errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
allow_direct
which enables the creation of streams on servers that supported that enable the direct api which may provide better performance on gets for KV.