Description of changes:
Construct stream ARNs (using the Kinesis client's configured region) for all stream configs upon writing to the currentStreamConfigMap in multi-stream mode.
This should ensure that all Kinesis API requests from KinesisDataFetcher and KinesisShardDetector are provided with the stream ARN in multi-stream applications.
Note: An implication of stream ARNs being used for Kinesis API calls is that the accountId provided through the StreamTracker must be correct, whereas previously applications may have consumed the streams as long as the provided streamName existed in the account that the Kinesis client was configured for.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: N/A.
Description of changes: Construct stream ARNs (using the Kinesis client's configured region) for all stream configs upon writing to the
currentStreamConfigMapin multi-stream mode. This should ensure that all Kinesis API requests fromKinesisDataFetcherandKinesisShardDetectorare provided with the stream ARN in multi-stream applications.Note: An implication of stream ARNs being used for Kinesis API calls is that the
accountIdprovided through theStreamTrackermust be correct, whereas previously applications may have consumed the streams as long as the providedstreamNameexisted in the account that the Kinesis client was configured for.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.