fix to readme required it seems

[DaReBeL]

Hi!
Kindly asking you to mention somehow on the readme what the scheduler-epoch value HAVE to be a string but not a long value, as it looking like in example currently. I just spent almost two days trying to figure out why nothing is working, and the reason was that the longs were passed instead of strings :) So it may help someone I hope.

Thank you!

[fkarakas]

Hello @DaReBeL sorry to hear that :(
I will update the readme and add double quote so it will be clear, WDYT ?

Headers:
    scheduler-epoch: "1893456000"
    scheduler-target-topic: "online-videos"
    scheduler-target-key: "vid1"
    customer-header: "dummy"
Timestamp: 1607918336
Key: "vid1-online"
Value: "video 1"

[DaReBeL]

Great, thanks! Hope that's make someone's life a bit easier.

[fkarakas]

👍 how do you plan to use the scheduler ? just a feedback for us, "feedback is a gift" :))

[DaReBeL]

Exactly in the way it is designed for. We have a need to postpone some request processing in async manner in our project. And since we are using kafka then your project fits quite well our needs, it seems :) But, actually, it's not a time for feedbacks yet, as we right on the "implementing" way in our project, so no real usage and no real experience as for now.

Anyway, thank you for this product, it's quite handy, I do believe.