Release 1.11.1 of the Amazon Kinesis Client Library for Java

Release 1.11.1 (August 9, 2019)

Milestone#34

• Updated the version of the AWS Java SDK to 1.11.603.
  • PR #587
• Added logging to KinesisDataFetcher when reaching the end of a shard due to a null next iterator.
  • PR #585

Release 1.11.0 of the Amazon Kinesis Client Library for Java

Release 1.11.0 (August 7, 2019)

Milestone#33

• Updated the version of the AWS Java SDK to 1.11.603
• Improved exception handling and logging in KinesisClientLibLeaseCoordinator to avoid NullPointerExceptions when no leases are found.
  • PR #558
• Introducing optional new periodic shard sync strategy to perform shard discovery and lease cleanup on a single worker.
  • PR #579

Release 2.2.1 of the Amazon Kinesis Client Library for Java

Release 2.2.1 (June 28, 2019)

Milestone#32

• Add periodic logging for the state of the thread pool executor service. This service executes the async tasks submitted to and by the ShardConsumer.
• Add logging of failures from RxJava layer.
  • PR#559

Release 2.2.0 of the Amazon Kinesis Client Library for Java

Release 2.2.0 (April 8, 2019)

Milestone#31

• Updated License to Apache License 2.0
  • PR#523
• Introducing configuration for suppressing logs from ReadTimeoutExceptions caused while calling SubscribeToShard.
  Suppression can be configured by setting LifecycleConfig#readTimeoutsToIgnoreBeforeWarning(Count).
  • PR#528

Release 1.10.0 of the Amazon Kinesis Client Library for Java

Release 1.10.0 (April 8, 2019)

Milestone#31

• Updated License to Apache License 2.0
  • PR#522

Release 2.1.3 of the Amazon Kinesis Client Library for Java

Release 2.1.3 (March 18, 2019)

Milestone#30

• Added a message to recommend using KinesisClientUtil when an acquire timeout occurs in the FanOutRecordsPublisher.
  • PR#514
• Added a sleep between retries while waiting for a newly created stream consumer to become active.
  • PR#506
• Added timeouts on all futures returned from the DynamoDB and Kinesis clients.
  The timeouts can be configured by setting LeaseManagementConfig#requestTimeout(Duration) for DynamoDB, and PollingConfig#kinesisRequestTimeout(Duration) for Kinesis.
  • PR#518
• Upgraded to SDK version 2.5.10.
  • PR#518
• Artifacts for the Amazon Kinesis Client for Java are now signed by a new GPG key:

  pub   4096R/86368934 2019-02-14 [expires: 2020-02-14]
  uid                  Amazon Kinesis Tools <[email protected]>
  

Release 2.1.2 of the Amazon Kinesis Client for Java

Release 2.1.2 (February 18, 2019)

Milestone#29

• Fixed handling of the progress detection in the ShardConsumer to restart from the last accepted record, instead of the last queued record.
  • PR#492
• Fixed handling of exceptions when using polling so that it will no longer treat SdkExceptions as an unexpected exception.
  • PR#497
  • PR#502
• Fixed a case where lease loss would block the Scheduler while waiting for a record processor's processRecords method to complete.
  • PR#501

Release 2.1.1 of the Amazon Kinesis Client for Java

Release 2.1.1 (February 6, 2019)

Milestone#28

• Introducing SHUT_DOWN_STARTED state for the WorkerStateChangeListener.
  • PR#457
• Fixed a bug with AWSSessionCredentials using AWSSecretID instead of AWSAccessID and vice versa.
  • PR#486
• Upgrading SDK version to 2.4.0, which includes a fix for a possible deadlock when using Enhanced Fan-Out.
  • PR#493

Release 2.1.0 of the Amazon Kinesis Client for Java

Release 2.1.0 (January 14, 2019)

Milestone #27

• Introducing MultiLangDaemon support for Enhanced Fan-Out.
• MultiLangDaemon now supports the following command line options.
  • --properties-file: Properties file that the KCL should use to set up the Scheduler.
  • --log-configuration: logback.xml that the KCL should use for logging.
• Updated AWS SDK dependency to 2.2.0.
• MultiLangDaemon now uses logback for logging.

Release 2.0.5 of the Amazon Kinesis Client for Java

Release 2.0.5 (November 12, 2018)

Milestone #26

• Fixed a deadlock condition that could occur when using the polling model.
  When using the PollingConfig and a slower record processor it was possible to hit a deadlock in the retrieval of records.
  • PR #462
  • Issue #448
• Adjusted RetrievalConfig, and FanOutConfig to use accessors instead of direct member access.
  • PR #453