Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting up the http.request.body field #94

Closed
igrishaev opened this issue Jan 21, 2021 · 2 comments
Closed

Setting up the http.request.body field #94

igrishaev opened this issue Jan 21, 2021 · 2 comments
Labels
question Further information is requested

Comments

@igrishaev
Copy link

Hello!

First, thank you for the library, that's really great to have a free version of HTTP connector (compared to the one from Confluent which is paid). My first question is, how can I put the message's payload into the body of the request. I'm expecting to have something like:

"http.request.body": "${message.payload}"

or similar (assuming that the messages from a topic are in JSON). But this doesn't work.

The more general question is, how can I know all the possible fields that I reference in the template? I know you use Freemaker as a template engine, but what is the context for it?

Thank you,
Ivan

@igrishaev
Copy link
Author

Sorry, it looks like misunderstood something. I thought that the library provides an HTTP Sink functionality so I could redirect JSON messages out from the topic to an HTTP endpoint. But judging by the #26 it's not possible at the moment, so my question is obsolete I guess.

@castorm
Copy link
Owner

castorm commented Jan 25, 2021

Hello @igrishaev ,

You are right, this connector only implements an HTTP Source, not Sink.

Maybe at some point in the future it will, but for now I'm afraid it doesn't. :(

Best regards.

@castorm castorm added the question Further information is requested label Jan 25, 2021
@castorm castorm closed this as completed Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants