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
Support Verbose API for scheduled and blocking bucket #483
Comments
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
Apr 30, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
Apr 30, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
Apr 30, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 1, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 1, 2024
vladimir-bukhtoyarov
pushed a commit
that referenced
this issue
May 1, 2024
Will be released in the scope of |
vladimir-bukhtoyarov
changed the title
Support Verbose API for sheduled and blocking bucket
Support Verbose API for scheduled and blocking bucket
May 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally asked there #482
Decision why it was declined at orignial #117 described there #483 (comment)
#482 (comment) describes decision why idea to add
bucket.asBlocking().asVerbose()
andbucket.asScheduler().asVerbose()
has been ressurected.P.S.
It needs to especiialy to mention in Javadoc and Reference that the main purpuse of VerboseResult is providing the answer why any method returns concrete result. Providing most fresh snapshot is not a goal.
The text was updated successfully, but these errors were encountered: