[BUG] "Expected value to be a 32-bit integer, but it was a java.lang.Long"

[PauloTemenos]

The Kafka input plugin looks to have a bug - numeric properties (I tracked around 3 properties before I gave up on «numeric» properties) do not work with, apparently, the number converted to Long then tried to downgrade-cast into Int.

I tried uninstalling the plugin and force-install version 7.1.1, but that version didn't work any better.

These are the 3 properties I tracked for sure to be suffering from this:
fetch_max_wait_ms
heartbeat_interval_ms
max_poll_interval_ms

• Version: Logstash 6.4.2 downloaded this morning;

• Operating System: Window 10

• Error output: "Invalid value 200 for configuration heartbeat.interval.ms: Expected value to be a 32-bit integer, but it was a java.lang.Long"

• Config File:

  # stdin { }
  kafka
  {
    #auto_commit_interval_ms => 5000
    #auto_offset_reset => earliest
    auto_offset_reset => latest
    enable_auto_commit => true
    
    bootstrap_servers => "localhost:9092"
    check_crcs => false
    client_id => "logstash-42"
    group_id => "logstash2"
    consumer_threads => 1
    decorate_events => true
    #exclude_internal_topics => false
    #fetch_max_bytes => 123
    #fetch_min_bytes => 1
    #fetch_max_wait_ms => 10000 #Expected value to be a 32-bit integer, but it was a java.lang.Long
    #poll_timeout_ms => 10001
    #request_timeout_ms => 25000
    #retry_backoff_ms => 500
    #heartbeat_interval_ms => 200 #Invalid value 200 for configuration heartbeat.interval.ms: Expected value to be a 32-bit integer, but it was a java.lang.Long
    #jaas_path => ""
    #max_partition_fetch_bytes => 4096
    #max_poll_interval_ms => 250 #Expected value to be a 32-bit integer, but it was a java.lang.Long
    #max_poll_records => 100
    #partition_assignment_strategy => "qwerty"
    #security_protocol => "PLAINTEXT"
    #session_timeout_ms => 
    topics => [ "test" ]
    #topics_pattern => ""
    #value_deserializer_class => "org.apache.kafka.common.serialization.StringDeserializer"
  }
}

[AlessandroMenti]

@PauloTemenos Did you try specifying the numeric properties as strings, like this?

request_timeout_ms => "25000"

This looks suspiciously similar to #199.