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.
-
Step 1: Migrate the record processor
Follow the Migrate the record processor
section in the Migrate consumers from KCL 1.x to KCL 2.x page. -
Step 2: Migrate the record processor factory
Follow the Migrate the record processor factory
section in the Migrate consumers from KCL 1.x to KCL 2.x page. -
Step 3: Migrate the worker
Follow the Migrate the worker
section in the Migrate consumers from KCL 1.x to KCL 2.x page. -
Step 4: Migrate KCL 1.x configuration
Follow the Configure the Amazon Kinesis client
section in the Migrate consumers from KCL 1.x to KCL 2.x page. -
Step 5: Check idle time removal and client configuration removals
Follow the Idle time removal
and Client configuration removals sections in the Migrate consumers from KCL 1.x to KCL 2.x page. -
Step 6: Follow the step-by-step instructions in the KCL 2.x to KCL 3.x migration guide
Follow instructions on the Migrate from KCL 2.x to KCL 3.x page to complete the migration. If you need to roll back to the previous KCL version or roll forward to KCL 3.x after a rollback, refer to Roll back to the previous KCL version and Roll forward to KCL 3.x after a rollback.
Important
Do not use AWS 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 AWS SDK for Java version 2.28.0 or later to avoid this issue.