Resetting the ScanPaginator

[reckerdaniel]

Hopefully this is a straightforward question. I am wondering what the best practice for resetting a ScanPaginator is.

Right now what i'm trying to do is

var firstToken map[string]types.AttributeValue
if scanPaginator.firstPage {
	firstToken = scanPaginator.nextToken
}
...
# Code that Gets all of the pages and does work on them
...
# Reset the values back to their starting phase
scanPaginator.nextToken = firstToken
scanPaginator.firstPage = true

Will this work as intended or is there a better way that i'm missing? The system is not setup to actually use DynamoDB locally it's using mocked out methods so i'm having trouble confirming if this would work in my production environment

Edit:
For context i am using the code from here
https://github.com/aws/aws-sdk-go-v2/blob/main/service/dynamodb/api_op_Scan.go

[jasdel]

Currently there is no way to reset the scan paginator. You'd need to recreate the paginator with the original input. The passed in input shouldn't be mutated by the paginator so you should be able to create a new paginator from the same input value.

[reckerdaniel]

Thanks Jason, Is there any plan to add some reset functionality to the scanner?

If not that's ok I can just create a new one to query DynamoDB again

[jasdel]

Is there any plan to add some reset functionality to the scanner

Not currently, no. The primary reason for this is the low overhead of creating a paginator. Reset would need growing the paginator paginator to persist both "next operation call input" and the original input, in case of reset.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.