All Versions
68
Latest Version
Avg Release Cycle
47 days
Latest Release
43 days ago

Changelog History
Page 5

  • v0.5.0.1 Changes

    • ๐Ÿ›  Fixed inconsistency in responders non-required topic definition. Now only required: false available
    • #101 - Responders fail when multiple_usage true and required false
    • ๐Ÿ›  fix error on startup from waterdrop #102
    • Waterdrop 0.3.2.1 with kafka.hosts instead of kafka_hosts
    • #105 - Karafka::Monitor#caller_label not working with inherited monitors
    • #99 - Standalone mode (without Sidekiq)
    • #97 - Buffer responders single topics before send (pre-validation)
    • ๐Ÿ‘ Better control over consumer thanks to additional config options
    • ๐Ÿ‘ท #111 - Dynamic worker assignment based on the income params
    • Long shutdown time fix
  • v0.4.2 Changes

    • ๐Ÿš… #87 - Re-consume mode with crone for better Rails/Rack integration
    • ๐Ÿšš Moved Karafka server related stuff into separate Karafka::Server class
    • ๐Ÿ“‡ Renamed Karafka::Runner into Karafka::Fetcher
    • Gem bump
    • โž• Added chroot option to Zookeeper options
    • ๐Ÿšš Moved BROKERS_PATH into config from constant
    • โž• Added Karafka consume CLI action for a short running single consumption round
    • ๐Ÿ›  Small fixes to close broken connections
    • โšก๏ธ Readme updates
  • v0.4.1 Changes

    • ๐Ÿš… Explicit throw(:abort) required to halt before_enqueue (like in Rails 5)
    • #61 - autodiscovery of Kafka brokers based on Zookeeper data
    • #63 - Graceful shutdown with current offset state during data processing
    • #65 - Example of NewRelic monitor is outdated
    • #71 - Setup should be executed after user code is loaded
    • Gem bump x3
    • Rubocop remarks
    • ๐Ÿšš worker_timeout config option has been removed. It now needs to be defined manually by the framework user because WorkerGlass::Timeout can be disabled and we cannot use Karafka settings on a class level to initialize user code stuff
    • ๐Ÿšš Moved setup logic under setup/Setup namespace
    • ๐Ÿ‘ Better defaults handling
    • #75 - Kafka and Zookeeper options as a hash
    • #82 - Karafka autodiscovery fails upon caching of configs
    • ๐Ÿ”ง #81 - Switch config management to dry configurable
    • ๐Ÿ”– Version fix
    • โฌ‡๏ธ Dropped support for Ruby 2.1.*
    • ๐Ÿ’Ž Ruby bump to 2.3.1
  • v0.4.0 Changes

    • โž• Added WaterDrop gem with default configuration
    • โ™ป๏ธ Refactoring of config logic to simplify adding new dependencies that need to be configured based on #setup data
    • Gem bump
    • โšก๏ธ Readme updates
    • ๐Ÿ“‡ Renamed cluster to actor_cluster for method names
    • ๐Ÿ‘ท Replaced SidekiqGlass with generic WorkerGlass lib
    • Application bootstrap in app.rb no longer required
    • โšก๏ธ Karafka.boot needs to be executed after all the application files are loaded (template updated)
    • โ™ป๏ธ Small loader refactor (no API changes)
    • 0๏ธโƒฃ Ruby 2.3.0 support (default)
    • No more rake tasks
    • Karafka CLI instead of rake tasks
    • ๐Ÿ‘ท Worker cli command allows passing additional options directly to Sidekiq
    • ๐Ÿ“‡ Renamed concurrency to max_concurrency - it describes better what happens - Karafka will use this number of threads only when required
    • โž• Added wait_timeout that allows us to tune how long should we wait on a single socket connection (single topic) for new messages before going to next one (this applies to each thread separately)
    • Rubocop remarks
    • โœ‚ Removed Sinatra and Puma dependencies
    • Karafka Cli internal reorganization
    • Karafka Cli routes task
    • ๐Ÿ“œ #37 - warn log for failed parsing of a message
    • #43 - wrong constant name
    • #44 - Method name conflict
    • #48 - Cannot load such file -- celluloid/current
    • #46 - Loading application
    • #45 - Set up monitor in config
    • #47 - rake karafka:run uses app.rb only
    • โšก๏ธ #53 - README update with Sinatra/Rails integration description
    • #41 - New Routing engine
    • ๐Ÿšš #54 - Move Karafka::Workers::BaseWorker to Karafka::BaseWorker
    • ๐Ÿ‘ท #55 - ApplicationController and ApplicationWorker
  • v0.3.2 Changes

    • ๐Ÿ”€ Karafka::Params::Params lazy load merge keys with string/symbol names priorities fix
  • v0.3.1 Changes

    • ๐Ÿ“‡ Renamed Karafka::Monitor to Karafka::Process to represent a Karafka process wrapper
    • โž• Added Karafka::Monitoring that allows to add custom logging and monitoring with external libraries and systems
    • ๐Ÿšš Moved logging functionality into Karafka::Monitoring default monitoring
    • โž• Added possibility to provide own monitoring as long as in responds to #notice and #notice_error
    • ๐Ÿ”Š Standardized logging format for all logs
  • v0.3.0 Changes

    • ๐Ÿ‘€ Switched from custom ParserError for each parser to general catching of Karafka::Errors::ParseError and its descendants
    • Gem bump
    • ๐Ÿ›  Fixed #32 - now when using custom workers that does not inherit from Karafka::BaseWorker perform method is not required. Using custom workers means that the logic that would normally lie under #perform, needs to be executed directly from the worker.
    • ๐Ÿ›  Fixed #31 - Technically didn't fix because this is how Sidekiq is meant to work, but provided possibility to assign custom interchangers that allow to bypass JSON encoding issues by converting data that goes to Redis to a required format (and parsing it back when it is fetched)
    • Added full parameters lazy load - content is no longer loaded during #perform_async if params are not used in before_enqueue
    • 0๏ธโƒฃ No more namespaces for Redis by default (use separate DBs)
  • v0.1.21 Changes

    • Sidekiq 4.0.1 bump
    • Gem bump
    • โž• Added direct celluloid requirement to Karafka (removed from Sidekiq)
  • v0.1.19 Changes

    • โฑ Internal call - schedule naming change
    • Enqueue to perform_async naming in controller to follow Sidekiqs naming convention
    • Gem bump
  • v0.1.18 Changes

    • ๐Ÿ”„ Changed Redis configuration options into a single hash that is directly passed to Redis setup for Sidekiq
    • โž• Added config.ru to provide a Sidekiq web UI (see README for more details)