V1.0 garble and V2.0 doesn't send result to Kafka.

[jackpgao]

• I use two version of goflow to decode sflow data, and found the flowing problem:

./goflow-linux-x86_64  -kafka.out.brokers xxxxxxxa.com.cn:9092  -kafka.out.topic vflow -loglevel debug -sworkers 10


./goflow-v2.0.1-linux-x86_64   -kafka.out.brokers xxxxx.com.cn:9092  -kafka.out.topic vflow  -loglevel debug -sworkers 10

• the first one send data to kafka, but it's all garbled.

• the second can do decode, but doesn't send data to Kafka.

[rzerda]

@jackpgao I believe that's not garbled but protobuf, which is binary format. I sucessfully run 1.1.0.

I had the same problem with 2.0.1, so created a MR #5. That change helped.

[jackpgao]

@alexey-dushechkin

Thanks for your reply.

Your PR seems lacks something:

 type KafkaState struct {
        producer sarama.AsyncProducer
+    topic *string

• Another question, why it use binary format? For performance? How can I read it?

[jackpgao]

• I've got it how to translate the binary to plain text.
• By the way, the binary format is more efficiency: https://webcache.googleusercontent.com/search?q=cache:55dv6nGSoPoJ:https://www.datadoghq.com/blog/engineering/protobuf-parsing-in-python/+&cd=1&hl=en&ct=clnk

[lspgn]

Just tested with @alexey-dushechkin patch, the Kafka issue is fixed in version 2.0.2.

The binary version is mostly for size and performance.