Skip to content
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

[YSQL] Investigate whether we can avoid read restart errors on filtered out rows #25444

Open
1 task done
pao214 opened this issue Dec 27, 2024 · 0 comments
Open
1 task done
Assignees
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug priority/low Low priority

Comments

@pao214
Copy link
Contributor

pao214 commented Dec 27, 2024

Jira Link: DB-14687

Description

FilteringIterator operates at a higher layer than IntentAwareIterator. Since read restart errors are detected, at the IntentAwareIterator level, rows filtered out at FilteringIterator can still cause read restart errors. Investigate whether we can avoid read restart errors in such a scenario.

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@pao214 pao214 added area/ysql Yugabyte SQL (YSQL) status/awaiting-triage Issue awaiting triage labels Dec 27, 2024
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels Dec 27, 2024
@pao214 pao214 self-assigned this Dec 27, 2024
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Dec 27, 2024
@pao214 pao214 added priority/low Low priority and removed priority/medium Medium priority issue labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/bug This issue is a bug priority/low Low priority
Projects
Status: No status
Development

No branches or pull requests

2 participants