1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
2
This is something the team are currently working on. When you use Limit you are not returned a NextToken, but a LastEvaluatedKey, and due to the lack of ExclusiveStartKey it cannot be used for Pagination. Unfortunately I do not have an ETA on the fix, but it is being worked on priority.
For now, if you are using Query you can alter your request to add the SK of the LastEvaluatedKey:
SELECT * FROM mytable WHERE PK='x' AND SK > {SK returned in LEK}
Hope that helps
관련 콘텐츠
AWS 공식업데이트됨 2년 전
@Leeroy,
Also running into this issue with first ExecuteStatement. But I do get a "NextToken" returned but when we fed it into the next "ExecuteStatement" as part of input, we keep getting an error "NextToken does not match request".