You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Map based config doesn't automatically merge config values, which means that each environment, if changing a consumer, must define the _entire_ consumer's config.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
# 2.0.0
2
+
3
+
### Breaking Changes
4
+
5
+
* Allow keyword configuration for subscribers. Note, keywords require atom keys, so if your current version of `kaffe` is 1.27.0 or higher, adopting to the keyword subscribers is a breaking (and highly encouraged) change.
topics: ["interesting-topic"], # the topic(s) that will be consumed
208
+
consumer_group:"your-app-consumer-group", # the consumer group for tracking offsets in Kafka
209
+
message_handler:MessageProcessor, # the module from Step 1 that will process messages
210
+
211
+
# optional
212
+
async_message_ack:false, # see "async message acknowledgement" below
213
+
start_with_earliest_message:true# default false
214
+
]
215
+
]
214
216
```
215
217
216
218
The `start_with_earliest_message` field controls where your consumer group starts when it starts for the very first time. Once offsets have been committed to Kafka then they will supercede this option. If omitted, your consumer group will start processing from the most recent messages in the topic instead of consuming all available messages.
@@ -221,11 +223,13 @@ _For backward compatibility only! `Kaffe.GroupMemberSupervisor` is recommended i
0 commit comments