karafka 2.5.9 → 2.6.0.beta1

data/lib/karafka/routing/features/eofed/contracts/topic.rb

@@ -1,37 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class Eofed < Base
-        # Eofed related contracts namespace
-        module Contracts
-          # Contract for eofed topic setup
-          class Topic < Karafka::Contracts::Base
-            configure do |config|
-              config.error_messages = YAML.safe_load_file(
-                File.join(Karafka.gem_root, "config", "locales", "errors.yml")
-              ).fetch("en").fetch("validations").fetch("routing").fetch("topic")
-            end
-
-            nested :eofed do
-              required(:active) { |val| [true, false].include?(val) }
-            end
-
-            virtual do |data, errors|
-              next unless errors.empty?
-
-              eofed = data[:eofed]
-
-              next unless eofed[:active]
-
-              next if data[:kafka][:"enable.partition.eof"]
-
-              [[%i[eofed kafka], :enable]]
-            end
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/eofed/topic.rb

@@ -1,40 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class Eofed < Base
-        # Routing topic eofed API
-        module Topic
-          # This method calls the parent class initializer and then sets up the
-          # extra instance variable to nil. The explicit initialization
-          # to nil is included as an optimization for Ruby's object shapes system,
-          # which improves memory layout and access performance.
-          def initialize(...)
-            super
-            @eofed = nil
-          end
-
-          # @param active [Boolean] should the `#eofed` job run on eof
-          def eofed(active = false)
-            @eofed ||= Config.new(
-              active: active
-            )
-          end
-
-          # @return [Boolean] Are `#eofed` jobs active
-          def eofed?
-            eofed.active?
-          end
-
-          # @return [Hash] topic setup hash
-          def to_h
-            super.merge(
-              eofed: eofed.to_h
-            ).freeze
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/eofed.rb

@@ -1,14 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      # Namespace for feature allowing to enable the `#eofed` jobs.
-      # We do not enable it always because users may only be interested in fast eofed yielding
-      # without running the `#eofed` operation at all. This safes on empty cycles of running
-      # pointless empty jobs.
-      class Eofed < Base
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/inline_insights/config.rb

@@ -1,15 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class InlineInsights < Base
-        # Config of this feature
-        Config = Struct.new(
-          :active,
-          keyword_init: true
-        ) { alias_method :active?, :active }
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/inline_insights/contracts/topic.rb

@@ -1,25 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class InlineInsights < Base
-        # Inline Insights related contracts namespace
-        module Contracts
-          # Contract for inline insights topic setup
-          class Topic < Karafka::Contracts::Base
-            configure do |config|
-              config.error_messages = YAML.safe_load_file(
-                File.join(Karafka.gem_root, "config", "locales", "errors.yml")
-              ).fetch("en").fetch("validations").fetch("routing").fetch("topic")
-            end
-
-            nested :inline_insights do
-              required(:active) { |val| [true, false].include?(val) }
-            end
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/inline_insights/topic.rb

@@ -1,40 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class InlineInsights < Base
-        # Routing topic inline insights API
-        module Topic
-          # This method calls the parent class initializer and then sets up the
-          # extra instance variable to nil. The explicit initialization
-          # to nil is included as an optimization for Ruby's object shapes system,
-          # which improves memory layout and access performance.
-          def initialize(...)
-            super
-            @inline_insights = nil
-          end
-
-          # @param active [Boolean] should inline insights be activated
-          def inline_insights(active = false)
-            @inline_insights ||= Config.new(
-              active: active
-            )
-          end
-
-          # @return [Boolean] Are inline insights active
-          def inline_insights?
-            inline_insights.active?
-          end
-
-          # @return [Hash] topic setup hash
-          def to_h
-            super.merge(
-              inline_insights: inline_insights.to_h
-            ).freeze
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/inline_insights.rb

@@ -1,40 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      # Feature allowing us to get visibility during the consumption into metrics of particular
-      # partition we operate on. It can be useful when making context-aware consumers that change
-      # their behaviours based on the lag and other parameters.
-      class InlineInsights < Base
-        class << self
-          # If needed installs the needed listener and initializes tracker
-          #
-          # @param _config [Karafka::Core::Configurable::Node] app config
-          def post_setup(_config)
-            Karafka::App.monitor.subscribe("app.running") do
-              # Do not activate tracking of statistics if none of our active topics uses it
-              # This prevents us from tracking metrics when user just runs a subset of topics
-              # in a given process and none of those actually utilizes this feature
-              next unless Karafka::App
-                .subscription_groups
-                .values
-                .flat_map(&:itself)
-                .flat_map(&:topics)
-                .flat_map(&:to_a)
-                .any?(&:inline_insights?)
-
-              # Initialize the tracker prior to becoming multi-threaded
-              Karafka::Processing::InlineInsights::Tracker.instance
-
-              # Subscribe to the statistics reports and collect them
-              Karafka.monitor.subscribe(
-                Karafka::Processing::InlineInsights::Listener.new
-              )
-            end
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/manual_offset_management/config.rb

@@ -1,15 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class ManualOffsetManagement < Base
-        # Config for manual offset management feature
-        Config = Struct.new(
-          :active,
-          keyword_init: true
-        ) { alias_method :active?, :active }
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/manual_offset_management/contracts/topic.rb

@@ -1,25 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class ManualOffsetManagement < Base
-        # This feature validation contracts
-        module Contracts
-          # Rules around manual offset management settings
-          class Topic < Karafka::Contracts::Base
-            configure do |config|
-              config.error_messages = YAML.safe_load_file(
-                File.join(Karafka.gem_root, "config", "locales", "errors.yml")
-              ).fetch("en").fetch("validations").fetch("routing").fetch("topic")
-            end
-
-            nested :manual_offset_management do
-              required(:active) { |val| [true, false].include?(val) }
-            end
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/manual_offset_management/topic.rb

@@ -1,44 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      class ManualOffsetManagement < Base
-        # Topic extensions to be able to manage manual offset management settings
-        module Topic
-          # This method calls the parent class initializer and then sets up the
-          # extra instance variable to nil. The explicit initialization
-          # to nil is included as an optimization for Ruby's object shapes system,
-          # which improves memory layout and access performance.
-          def initialize(...)
-            super
-            @manual_offset_management = nil
-          end
-
-          # @param active [Boolean] should we stop managing the offset in Karafka and make the user
-          #   responsible for marking messages as consumed.
-          # @return [Config] defined config
-          #
-          # @note Since this feature supports only one setting (active), we can use the old API
-          # where the boolean would be an argument
-          def manual_offset_management(active = false)
-            @manual_offset_management ||= Config.new(active: active)
-          end
-
-          # @return [Boolean] is manual offset management enabled for a given topic
-          def manual_offset_management?
-            manual_offset_management.active?
-          end
-
-          # @return [Hash] topic with all its native configuration options plus manual offset
-          #   management namespace settings
-          def to_h
-            super.merge(
-              manual_offset_management: manual_offset_management.to_h
-            ).freeze
-          end
-        end
-      end
-    end
-  end
-end

data/lib/karafka/routing/features/manual_offset_management.rb

@@ -1,18 +0,0 @@
-# frozen_string_literal: true
-
-module Karafka
-  module Routing
-    module Features
-      # All the things needed to be able to manage manual offset management from the routing
-      # perspective.
-      #
-      # Manual offset management allows users to completely disable automatic management of the
-      # offset. This can be used for implementing long-living window operations and other things
-      # where we do not want to commit the offset with each batch.
-      #
-      # Not all the Karafka and Karafka Pro features may be compatible with this feature being on.
-      class ManualOffsetManagement < Base
-      end
-    end
-  end
-end