logstash-input-kafka 2.0.9 → 2.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: ed5d842f321337ccdffd5748b51427d448cc5cff
4
- data.tar.gz: 413faa89d632a270e25543b4ed16fff60769ac36
3
+ metadata.gz: b5ae836d613cddbb4afc4b9789ffb96e5133703d
4
+ data.tar.gz: 3b200feb6e0b8096ccd6f211cc8903e920599e45
5
5
  SHA512:
6
- metadata.gz: 1c1999615ac3b07088037e481fd0b332f16be0ecd4280c2e012c6c372b81d9b8c1cdaf89df73712d98f1d7b7cb5d68e978aa434648be14e5845382e8c1c9cf45
7
- data.tar.gz: a89e66eff7255cb6f7882b88b4f237635e0cd565399675462935f3687a902d44ddea6b862ba916bffa8330ec6de188da93e5551c5350c86ee620008689d4b8d1
6
+ metadata.gz: 6fc55d881fb22f59a2455efa4e654c570d0eefa08c6cc62d429e4dfe67eb0b83eadfc7c6ee97ddd869e880c0f43afda3a99b64839b34904d9cefd8208f688c32
7
+ data.tar.gz: 779f59d1de7ba09b9ec5f3022de0059bf34e10feec22572012412b46d59e55d30ba76d166f02d4274d93202d28a93c1afc76d6ead6181c31f23b1bd91f5f9383
data/CHANGELOG.md CHANGED
@@ -1,3 +1,6 @@
1
+ # 2.1.0
2
+ - Users can now use custom log4j file to control logging output.
3
+
1
4
  # 2.0.9
2
5
  - Fix shutdown sequence bug where a shutdown event found itself in queue after a shutdown was initiated
3
6
 
@@ -5,10 +5,25 @@ require 'stud/interval'
5
5
 
6
6
  # This input will read events from a Kafka topic. It uses the high level consumer API provided
7
7
  # by Kafka to read messages from the broker. It also maintains the state of what has been
8
- # consumed using Zookeeper. The default input codec is json
8
+ # consumed using Zookeeper. The default input codec is json.
9
+ #
10
+ # Here's a compatibility matrix that shows the Kafka broker and client versions that are compatible with each combination
11
+ # of Logstash and the Kafka input plugin:
12
+ #
13
+ # [options="header"]
14
+ # |==========================================================
15
+ # |Kafka Broker Version |Kafka Client Version |Logstash Version |Plugin Version |Why?
16
+ # |0.8 |0.8 |2.0.0 - 2.x.x |<3.0.0 |Legacy, 0.8 is still popular
17
+ # |0.9 |0.9 |2.0.0 - 2.3.x | 3.x.x |Works with the old Ruby Event API (`event['product']['price'] = 10`)
18
+ # |0.9 |0.9 |2.4.0 - 5.0.x | 4.x.x |Works with the new getter/setter APIs (`event.set('[product][price]', 10)`)
19
+ # |0.10 |0.10 |2.4.0 - 5.0.x | 5.x.x |Not compatible with the 0.9 broker
20
+ # |==========================================================
21
+ #
22
+ # NOTE: It's a good idea to upgrade brokers before consumers/producers because brokers target backwards compatibility.
23
+ # For example, the 0.9 broker will work with both the 0.8 consumer and 0.9 consumer APIs, but not the other way around.
9
24
  #
10
25
  # You must configure `topic_id`, `white_list` or `black_list`. By default it will connect to a
11
- # Zookeeper running on localhost. All the broker information is read from Zookeeper state
26
+ # Zookeeper running on localhost. All the broker information is read from Zookeeper state.
12
27
  #
13
28
  # Ideally you should have as many threads as the number of partitions for a perfect balance --
14
29
  # more threads than partitions means that some threads will be idle
@@ -100,7 +115,6 @@ class LogStash::Inputs::Kafka < LogStash::Inputs::Base
100
115
 
101
116
  public
102
117
  def register
103
- LogStash::Logger.setup_log4j(@logger)
104
118
  options = {
105
119
  :zk_connect => @zk_connect,
106
120
  :group_id => @group_id,
@@ -1,7 +1,7 @@
1
1
  Gem::Specification.new do |s|
2
2
 
3
3
  s.name = 'logstash-input-kafka'
4
- s.version = '2.0.9'
4
+ s.version = '2.1.0'
5
5
  s.licenses = ['Apache License (2.0)']
6
6
  s.summary = 'This input will read events from a Kafka topic. It uses the high level consumer API provided by Kafka to read messages from the broker'
7
7
  s.description = "This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program"
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: logstash-input-kafka
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.9
4
+ version: 2.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Elasticsearch
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-07-07 00:00:00.000000000 Z
11
+ date: 2016-12-06 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  requirement: !ruby/object:Gem::Requirement