Releases: awslabs/amazon-kinesis-client
Releases · awslabs/amazon-kinesis-client
Experimental release of the Amazon Kinesis Client
Release 7
- Don't attempt to validate continuation sequence number when it's null
Experimental release of the Amazon Kinesis Client
Experimental Release 2.0.3-experimental-6
- Upgraded to AWS SDK 2.0.4
Experimental release of the Amazon Kinesis Client
Release 2.0.3-experimental-5
- Validate the continuation sequence number in SubscribeToShardEvent's as well as the records.
Experimental release of the Amazon Kinesis Client
- Log the
SubscribeToShardRequest
before making the request, and after connecting.
Experimental release of the Amazon Kinesis Client
- Log requestId of successful SubscribeToShard requests
- Validate sequence numbers in
advancePosition()
of the checkpointer to catch direct uses ofcheckpoint()
Experimental release of the Amazon Kinesis Client
- Added sequence number validation in the
ShardConsumer
- Added sequence number validation in the
ShardRecordProcessorCheckpointer
Experimental release of the Amazon Kinesis Client
This is an experimental release of the Amazon Kinesis Client for Java released to assist with tracking down possible record issues
Release 2.0.2 of the Amazon Kinesis Client
Release 2.0.2 (September 4, 2018)
- Fixed an issue where the a warning would be logged every second if
logWarningForTaskAfterMillis
was set.
The logging for last time of data arrival now respects the value oflogWarningForTaskAfterMillis
. - Moved creation of
WorkerStateChangedListener
andGracefulShutdownCoordinator
to theCoordinatorConfig
.
Originally theWorkerStateChangedListener
andGracefulShutdownCoordinator
were created by methods on theSchedulerCoordinatorFactory
, but they should have been configuration options.
The original methods have been deprecated, and may be removed at a later date. - Removed dependency on Apache Commons Lang 2.6.
The dependency on Apache Commons Lang 2.6 has removed, and all usages updated to use Apache Commons Lang 3.7. - Fixed a typo in the MutliLang Daemon shutdown hook.
- Added method
onAllInitializationAttemptsFailed(Throwable)
toWorkerStateChangedListener
to report when all initialization attempts have failed.
This method is a default method, and it isn't require to implement the method. This method is only called after all attempts to initialize theScheduler
have failed.
Release 1.9.2 of the Amazon Kinesis Client
Release 1.9.2 (September 4, 2018)
- Allow use of Immutable Clients
- Allow the use of
AT_TIMESTAMP
for MultiLang Daemon Clients.- [Issue #341)(https://github.com//issues/341)
- PR #342
- Update the cache for
KinesisProxy#getShard
on cache misses. - Changed release process to use a standard process.
- Removed tests that expected a null region response for unknown regions.
- Updated the version of the AWS Java SDK to 1.11.400
Release 2.0.1 of the Amazon Kinesis Client Library for Java
Release 2.0.1 (August 21, 2018)
- Mark certain internal components with
@KinesisClientInternalApi
attribute.
Components marked as internal may be deprecated at a faster rate than public components. - Fixed an issue where
ResourceNotFoundException
on subscription to a shard was not triggering end of shard handling.
If a lease table contains a shard that is no longer present in the stream attempt to subscribe to that shard will trigger aResourceNotFoundException
. These exception are treated the same as reaching the end of a shard. - Fixed an issue where the KCL would not Use the configured DynamoDB IOPs when creating the lease table.
- Make the maximum number of Scheduler initialization attempts configurable.
The maximum number ofScheduler
initialization attempts can be configured viaCoordinatorConfig#maxInitializationAttempts
. - Fixed an issue where it was possible to get a duplicate record when resubscribing to a shard.
Subscribe to shard requires periodic resubscribing, and uses a new concept of a continuation sequence number. If the continuation sequence number was equal to the last record that record would be processed a second time. Resubscribing now usesAFTER_SEQUENCE_NUMBER
to ensure that only later records are returned. - Upgraded to AWS SDK 2.0.1
- Fixed an issue where time based restart of the subscription wasn't resetting the
lastRequestTime
.
If a subscription hasn't delivered any data for more than 30 seconds it will be canceled and restarted. This detection is based of thelastRequestTime
which wasn't getting reset after the restart was triggered. - Fixed an issue where requesting on the subscription from the
FanOutRecordsPublisher
could trigger an unexpected failure.
Due to a race condition the underlying flow in the subscription could be set to something else. The method is now synchronized, and verifies that the subscriber it was created with is still the subscriber in affect.
This issue generally would only appear when multiple errors were occurring while connecting to Kinesis. - Fixed an issue where the number of requested items could exceed the capacity of the RxJava queue.
There was an off by one issue when determining whether to make a request to the SDK subscription. This changes the calculation to represent the capacity as a queue.