storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Jose <>
Subject Flux 2.2.0
Date Mon, 21 Sep 2020 06:35:26 GMT

My name is Paul. Previously I was using storm 0.10.0 and now have to upgrade to the latest
I am using flux. But it isn't working. This is my config:

name: "AuditLogConsumerTopology"


  - id: "kafkaConfigBuilder"
    className: "org.apache.storm.kafka.spout.KafkaSpoutConfig$Builder"
      # bootstrap servers
      - "localhost:9092"
      # topics
      - ["topic"]

  #Spout Config
  - id: "SpoutConfig"
    className: "org.apache.storm.kafka.spout.KafkaSpoutConfig"
      # brokerHosts
      - ref: "kafkaConfigBuilder"
      - name: ""
        value: "test-group"
      - name: "key.deserializer"
        value: "org.apache.kafka.common.serialization.StringDeserializer"
      - name: "value.deserializer"
        value: "org.apache.kafka.common.serialization.StringDeserializer"

  topology.workers: 1
  topology.max.spout.pending: 1000
  topology.acker.executors: 1
  topology.executor.send.buffer.size: 16384
  topology.executor.receive.buffer.size: 16384
  topology.transfer.buffer.size: 32
  zookeeperHost: "localhost"
  zookeeperBasePath: "platformaudit"
    #bootstrap.servers: "localhost:9092" "localhost:9092"
    request.required.acks: "1"
  topic: "topic"

  - id: "TestSpout"
    className: "org.apache.storm.kafka.spout.KafkaSpout"
    parallelism: 1
      - ref: "SpoutConfig"

  - id: "TestBolt"
    className: "auditlog.TestBolt"
    parallelism: 1
      - "auditlog"
      - "_doc"
      - localhost
      - 9200

  - name: "TestSpout --> TestBolt"
    from: "TesstSpout"
    to: "TestBolt"
      type: SHUFFLE

My changing the configuration by referring to the actual storm consumer 2.2.0 code I was able
to make this yaml flux file.

However I am unable to specify any properties from this yaml file for the consumer.

I tried giving "" and it gives an errror:

Exception in thread "main" java.lang.NoSuchFieldException: groupId

at java.lang.Class.getField(
at org.apache.storm.flux.FluxBuilder.findPublicField(
at org.apache.storm.flux.FluxBuilder.applyProperties(
at org.apache.storm.flux.FluxBuilder.buildObject(
at org.apache.storm.flux.FluxBuilder.buildComponents(
at org.apache.storm.flux.FluxBuilder.buildTopology(
at org.apache.storm.flux.Flux.runCli(
at org.apache.storm.flux.Flux.main(

Without specifying properties the topology does get submitted but it throws an error in the
spout saying:

java.lang.RuntimeException: org.apache.kafka.common.config.ConfigException: Missing required
configuration "key.deserializer" which has no default value. at org.apache.storm.utils.Utils$
at Caused by: org.apache.kafka.common.config.ConfigException:
Missing required configuration "key.deserializer" which has no default value. at org.apache.kafka.common.config.ConfigDef.parseValue(
at org.apache.kafka.common.config.ConfigDef.parse( at org.apache.kafka.common.config.AbstractConfig.<init>(
at org.apache.kafka.common.config.AbstractConfig.<init>( at
org.apache.kafka.clients.consumer.ConsumerConfig.<init>( at
org.apache.kafka.clients.consumer.KafkaConsumer.<init>( at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(
at org.apache.storm.kafka.spout.internal.ConsumerFactoryDefault.createConsumer(
at org.apache.storm.kafka.spout.internal.ConsumerFactoryDefault.createConsumer(
at at org.apache.storm.executor.spout.SpoutExecutor.init(
at at
at org.apache.storm.utils.Utils$ ... 1 more

I went through a bit of the source code and found this. The properties aren't there in the
"org.apache.storm.kafka.spout.KafkaSpoutConfig" file but in the "ConsumerConfig" file. So
when flux tries to get the field name given in the properties file it fails.

Previously in version 0.10.0 the configuration fields were available in the "storm.kafka.SpoutConfig"
file itself.

Can I please get some help on how to resolve this issue? The flux kafka spout example at ""
is also wrong. I am not sure if it has been updated.

Best Regards,

Paul Jose

****Views and opinions expressed in this e-mail belong to  their author and do not necessarily
represent views and opinions  of Ugam. 
Our employees are obliged not to make any defamatory statement or infringe any legal right.

Therefore, Ugam does not accept any responsibility or liability for such statements. The content
of this email is confidential and intended for the recipient specified in message only. It
is strictly forbidden to share any part of this message with any third party, without a written
consent of the sender.
If you have received this message by mistake, please reply to this message and follow with
its deletion, so that we can ensure such a mistake does not occur in the future. 
Warning: Sufficient measures have been taken to scan any presence of viruses however the recipient
should check this email and any attachments for the presence of viruses as full security of
the email cannot be ensured despite our best efforts.
Therefore, Ugam accepts no liability for any damage inflicted by viewing the content of this
email.. ****

Please do not print this email unless it is necessary. Every unprinted email helps the environment.

View raw message