lib/karafka/attributes_map.rb in karafka-1.0.1 vs lib/karafka/attributes_map.rb in karafka-1.1.0.alpha1
- old
+ new
@@ -19,11 +19,11 @@
consumer: %i[
session_timeout offset_commit_interval offset_commit_threshold
offset_retention_time heartbeat_interval
],
subscription: %i[start_from_beginning max_bytes_per_partition],
- consuming: %i[min_bytes max_wait_time],
+ consuming: %i[min_bytes max_wait_time automatically_mark_as_processed],
pausing: %i[pause_timeout],
# All the options that are under kafka config namespace, but are not used
# directly with kafka api, but from the Karafka user perspective, they are
# still related to kafka. They should not be proxied anywhere
ignored: %i[reconnect_timeout]
@@ -35,11 +35,11 @@
(config_adapter[:subscription] + %i[
backend
name
parser
responder
- batch_processing
+ batch_consuming
persistent
]).uniq
end
# @return [Array<Symbol>] properties that can be set on a per consumer group level
@@ -50,10 +50,10 @@
def consumer_group
# @note We don't ignore the config_adapter[:ignored] values as they should be ignored
# only when proxying details go ruby-kafka. We use ignored fields internally in karafka
ignored_settings = config_adapter[:subscription]
defined_settings = config_adapter.values.flatten
- karafka_settings = %i[batch_consuming]
+ karafka_settings = %i[batch_fetching]
# This is a drity and bad hack of dry-configurable to get keys before setting values
dynamically_proxied = Karafka::Setup::Config
._settings
.find { |s| s.name == :kafka }
.value