lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(job-array-one-based-index): row predicates in the apiserver query pipeline (task 5.3)

Browse source 
QueryOptions gains Predicates; store.ExecuteQuery keeps a row only if
every predicate returns true, after the plain conditions and before
sort, pagination and field selection, so page boundaries and tokens
count only matching rows. Nil/empty predicates leave every existing
query unchanged. Foundation for evaluating element selections
(bug-1898).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-01 11:35:05 +00:00
parent 7f417262c5
commit 46f57095c1
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
4 changed files with 177 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.kiro/specs/job-array-one-based-index/tasks.md
View file

@ -108,7 +108,7 @@
- _Requirements: 1.6, 1.7, 1.8, 1.9_
- _Boundary: ApiConfig_
- [ ] 5.3 (P) Evaluate row predicates in the query pipeline
- [x] 5.3 (P) Evaluate row predicates in the query pipeline
- Add row predicates to the query options and apply them after the plain conditions and before sorting and pagination
- Done when the store query tests show predicates filtering before pagination, with page boundaries and bookmarks consistent
- _Requirements: 5.2, 5.11_