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.
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
Optimize exec async #16
base: main
Are you sure you want to change the base?
Optimize exec async #16
Changes from 3 commits
3c4b3b9
68f4d21
3eb1364
2f8f985
841a5d9
55940c0
eb040ae
bf91ae7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
let's call this
gotCompleteResult
, notgotCompletedResult
, inline with the Go SDK: https://github.com/RelationalAI/rai-sdk-go/blob/bbc1c3bba86b43865e983d992d48161e5652530f/rai/models.go#L302-L303It doesn't mean that the transaction was completed, it means that it was either completed or aborted, and we got the results.
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.
I guess there are a few cases we're covering with this type:
ExecuteAsync
=> fast path; contains results. state isaborted
orcompleted
ExecuteAsync
=> slow path; doesn't contain results. state isrunning
Execute
=> regardless of path, contains results. eitheraborted
orcompleted
I guess
gotCompleteResult
differentiates (1) from (2)? But why do we need it? Can't we use the state to differentiate?What am I missing @NHDaly
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 discussed how in the original spec (before you joined the project, i think, @vilterp), we intended to have a fourth state:
4. ExecuteAsync => fast path; does not contain results (because they are too big to send over the wire, and you presumably want to page them). state is aborted or completed
So i think this isn't strictly needed right now; it's a future-proofing that you and I did while we were looking at the code.
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.
K thanks. I forgot that it was future proofing and not a case we need now.