Fixing bug where ShardFilter parameter for ListShards was being passed in for paginated calls.
This resulted in a bug where all calls for ListShards when initializing the lease table would fail, since Kinesis only requires the NextToken parameter when making paginated calls.
This commit is contained in:
parent
d5cac07851
commit
efc57af43f
1 changed files with 2 additions and 2 deletions
|
|
@ -192,9 +192,9 @@ public class KinesisShardDetector implements ShardDetector {
|
||||||
exceptionManager.add(ResourceInUseException.class, t -> t);
|
exceptionManager.add(ResourceInUseException.class, t -> t);
|
||||||
exceptionManager.add(KinesisException.class, t -> t);
|
exceptionManager.add(KinesisException.class, t -> t);
|
||||||
|
|
||||||
ListShardsRequest.Builder request = KinesisRequestsBuilder.listShardsRequestBuilder().shardFilter(shardFilter);
|
ListShardsRequest.Builder request = KinesisRequestsBuilder.listShardsRequestBuilder();
|
||||||
if (StringUtils.isEmpty(nextToken)) {
|
if (StringUtils.isEmpty(nextToken)) {
|
||||||
request = request.streamName(streamIdentifier.streamName());
|
request = request.streamName(streamIdentifier.streamName()).shardFilter(shardFilter);
|
||||||
} else {
|
} else {
|
||||||
request = request.nextToken(nextToken);
|
request = request.nextToken(nextToken);
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue