The DynamoDB documentation https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html says that:
If you disable a stream, any shards that are open will be closed. The data in the stream will continue to be readable for 24 hours.
However, in Alternator, we don't allow this. A new test test_streams.py::test_streams_closed_next tries to use shard iterators which were obtained before the stream was disabled, and the test shows that this is possible on DynamoDB, but generates an error on Alternator:
An error occurred (ResourceNotFoundException) when calling the GetRecords operation: cb8ff030-f74a-11ea-b0cc-000000000000
As far as I understand, there is no reason why this should not be allowed in Alternator as well; Disabling streaming does not (as far as I know) remove the existing stream data, so it should be just as usual as it was before. ListStreams should list the old stream (at least for 24 hours) - just DescribeStream should say it is DISABLED.
The DynamoDB documentation https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Streams.html says that:
However, in Alternator, we don't allow this. A new test
test_streams.py::test_streams_closed_nexttries to use shard iterators which were obtained before the stream was disabled, and the test shows that this is possible on DynamoDB, but generates an error on Alternator:As far as I understand, there is no reason why this should not be allowed in Alternator as well; Disabling streaming does not (as far as I know) remove the existing stream data, so it should be just as usual as it was before.
ListStreamsshould list the old stream (at least for 24 hours) - justDescribeStreamshould say it isDISABLED.