xiaokang opened a new pull request, #11757:
URL: https://github.com/apache/doris/pull/11757
fix orderby keys limit return less or no result when a WHERE predicte filter
most rows
# Proposed changes
Issue Number: close #xxx
## Problem summary
Describe your changes.
The bug is caused by use _num_rows_read for limit check. _num_rows_read is
count of rows read from storage, but may be filtered by filter_block for WHERE
predicate.
Add a _num_rows_return, which is rows after filter_block for WHERE
predicate, for count for really returned rows.
## Checklist(Required)
1. Does it affect the original behavior:
- [ ] Yes
- [x] No
- [ ] I don't know
2. Has unit tests been added:
- [ ] Yes
- [x] No
- [ ] No Need
3. Has document been added or modified:
- [ ] Yes
- [ ] No
- [x] No Need
4. Does it need to update dependencies:
- [ ] Yes
- [x] No
5. Are there any changes that cannot be rolled back:
- [ ] Yes (If Yes, please explain WHY)
- [x] No
## Further comments
If this is a relatively large or complex change, kick off the discussion at
[d...@doris.apache.org](mailto:d...@doris.apache.org) by explaining why you
chose the solution you did and what alternatives you considered, etc...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
