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
Let the m to n steps return the data even if can't reach n steps. #2148
Let the m to n steps return the data even if can't reach n steps. #2148
Conversation
…om:Shylock-Hg/nebula into correct/return-m-to-n-data-when-cant-reach
This reverts commit fbe28b7.
Codecov Report
@@ Coverage Diff @@
## master #2148 +/- ##
==========================================
- Coverage 86.84% 86.83% -0.01%
==========================================
Files 641 641
Lines 61651 62022 +371
==========================================
+ Hits 53541 53859 +318
- Misses 8110 8163 +53
Continue to review full report at Codecov.
|
@@ -695,8 +703,8 @@ void GoExecutor::finishExecution() { | |||
StatusOr<std::vector<cpp2::RowValue>> GoExecutor::toThriftResponse() const { | |||
std::vector<cpp2::RowValue> rows; | |||
int64_t totalRows = 0; | |||
for (const auto &rpcResp : records_) { | |||
for (const auto& resp : rpcResp.responses()) { | |||
for (auto rpcResp = records_.begin() + recordFrom_ - 1; rpcResp != records_.end(); ++rpcResp) { |
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.
Add a check?
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.
What check?
…soft-inc#2148) * Let the m to n steps return the data even if can't reach n steps. * Unify the go exit entry. * Revert "Unify the go exit entry." This reverts commit fbe28b7. * Unify the go exit entry. * Fix the edges reserve count. * Add a cases for record a part data in go. * Fix DAIL-91
What changes were proposed in this pull request?
Keep return data even if can't reach N steps.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?
Checklist