Skip to content

fix: skip DynamoDB Limit when FilterExpression is present#19

Merged
rauann merged 1 commit intomainfrom
improve-limit-query
Feb 20, 2026
Merged

fix: skip DynamoDB Limit when FilterExpression is present#19
rauann merged 1 commit intomainfrom
improve-limit-query

Conversation

@rauann
Copy link
Owner

@rauann rauann commented Feb 20, 2026

DynamoDB applies Limit before FilterExpression, so passing Limit=N evaluates only N items and may return far fewer after filtering — causing excessive pagination. The Paginator now omits Limit when a FilterExpression is present, letting DynamoDB evaluate its natural 1MB page while controlling the stopping logic internally.

Closes #18

@rauann rauann self-assigned this Feb 20, 2026
DynamoDB applies Limit before FilterExpression, so passing Limit=N
evaluates only N items and may return far fewer after filtering —
causing excessive pagination. The Paginator now omits Limit when a
FilterExpression is present, letting DynamoDB evaluate its natural 1MB
page while controlling the stopping logic internally.

Closes #18
@rauann rauann force-pushed the improve-limit-query branch from 93f8c29 to b74341a Compare February 20, 2026 21:07
@rauann rauann marked this pull request as ready for review February 20, 2026 21:11
@rauann rauann merged commit 1d02c55 into main Feb 20, 2026
1 check passed
@rauann rauann deleted the improve-limit-query branch February 21, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Limit + FilterExpression causes excessive DynamoDB requests

1 participant