View a markdown version of this page

Migrating from KCL 1.x to KCL 3.x - Amazon Kinesis Data Streams
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Migrating from KCL 1.x to KCL 3.x

This topic explains the instructions to migrate your consumer from KCL 1.x to KCL 3.x. KCL 1.x uses different classes and interfaces compared to KCL 2.x and KCL 3.x. You must migrate the record processor, record processor factory, and worker classes to the KCL 2.x/3.x compatible format first, and follow the migration steps for KCL 2.x to KCL 3.x migration. You can directly upgrade from KCL 1.x to KCL 3.x.

Important

We recommend that you migrate to KCL 3.5 or later, which uses single table format by default for new migrations. First, migrate your record processor, factory, and worker classes to the KCL 2.x/3.x compatible format using the steps on this page. Then, follow the migration path from KCL 2.x to KCL 3.5. Single table format is automatically enabled for new migrations from 2.x. For more information, see Single table format for KCL.

Important

Do not use Amazon SDK for Java version 2.27.19 to 2.27.23 with KCL 3.x. These versions include an issue that causes an exception error related to KCL's DynamoDB usage. We recommend that you use the Amazon SDK for Java version 2.28.0 or later to avoid this issue.