Update docs

Workable · Jul 3, 2024 · ae2f079 · ae2f079
1 parent c057664
commit ae2f079
Show file tree

Hide file tree

Showing 2 changed files with 24 additions and 0 deletions.
diff --git a/docs/index.md b/docs/index.md
@@ -75,3 +75,6 @@ ObjectId using new mongoose.
 - Changes in default config: istioTraceHeaders and headerPropagation are deprecated in favor of a generic propagatedHeaders
 - Methods kafka.send that was deprecated is removed. Use kafka.producer.send instead
 - Mongoose migrated to v7 which has breaking changes see [here](https://mongoosejs.com/docs/7.x/docs/migrating_to_7.html)
+
+### Migrating from orka  4.x to 5.x
+- Support for KafkaJS version pre 2.x.x is dropped.
diff --git a/docs/integrations/kafka.md b/docs/integrations/kafka.md
@@ -242,3 +242,24 @@ You also need to specify the new group ids in your consumers while previously yo
 Once the new group ids are created you can remove the code that copies their offsets from old group ids. This is causing no issues thought as it doesn't do anything if the new group ids are found with offsets set.
 
 If you are using the renameGroupIds (before creating your consumers) your consumers will continue reading messages from the offset specified from the old groupId regardless if you set the fromBeginning configuration. FromBeginning configuration will be used if the groupId, topic is not found in kafka.
+
+## Migrating from orka < 5.x.x
+
+Since Orka 5.x.x, the required KafkaJS version is ^2.x.x
+(more info on the KafkaJS changes [here](https://kafka.js.org/docs/migration-guide-v2.0.0))
+
+The only possible implication is the update of the DefaultPartitioner (https://kafka.js.org/docs/migration-guide-v2.0.0#producer-new-default-partitioner). This may case
+issues in partition-aware environments, since some messages may be produced in different partitions than they would with the previous default partitioner.
+
+By default, Orka ^5.x.x will use the new DefaultPartitioner (previously named JavaCompatiblePartitioner).
+You can use the previous DefaultPartitioner (now renamed to LegacyPartitioner) with:
+
+```js
+import { Partitioners } from 'kafkajs';
+
+builder({…some static options here…})
+  ...
+  .withKafka({ createPartitioner: Partitioners.LegacyPartitioner })
+  .start(8080);
+```
+