Kafka streams using context forward from processor called in dsl api
up vote
0
down vote
favorite
I have a processor and would like to call context.forward() in it. However I feel like I need to set a sink topic for it to actually get forwarded. If I was using the Toplogy I would just .addSource(), .addProcessor(), .addSink(). However with the DSL I have a StreamsBuilder/KStream. Is there anyway to use context.forward() when calling a processor from the dsl?
NOTE: I need to use a processor instead of a transform as I have custom logic on when to forward records down stream.
stream.process(() -> new WindowAggregatorProcessor(storeName), storeName);
apache-kafka-streams
asked Nov 13 at 22:25
Chris
3083416
add a comment |
up vote
0
down vote
favorite
I have a processor and would like to call context.forward() in it. However I feel like I need to set a sink topic for it to actually get forwarded. If I was using the Toplogy I would just .addSource(), .addProcessor(), .addSink(). However with the DSL I have a StreamsBuilder/KStream. Is there anyway to use context.forward() when calling a processor from the dsl?
NOTE: I need to use a processor instead of a transform as I have custom logic on when to forward records down stream.
stream.process(() -> new WindowAggregatorProcessor(storeName), storeName);
apache-kafka-streams
asked Nov 13 at 22:25
Chris
3083416
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a processor and would like to call context.forward() in it. However I feel like I need to set a sink topic for it to actually get forwarded. If I was using the Toplogy I would just .addSource(), .addProcessor(), .addSink(). However with the DSL I have a StreamsBuilder/KStream. Is there anyway to use context.forward() when calling a processor from the dsl?
NOTE: I need to use a processor instead of a transform as I have custom logic on when to forward records down stream.
stream.process(() -> new WindowAggregatorProcessor(storeName), storeName);
apache-kafka-streams
asked Nov 13 at 22:25
Chris
3083416
I have a processor and would like to call context.forward() in it. However I feel like I need to set a sink topic for it to actually get forwarded. If I was using the Toplogy I would just .addSource(), .addProcessor(), .addSink(). However with the DSL I have a StreamsBuilder/KStream. Is there anyway to use context.forward() when calling a processor from the dsl?
NOTE: I need to use a processor instead of a transform as I have custom logic on when to forward records down stream.
stream.process(() -> new WindowAggregatorProcessor(storeName), storeName);
apache-kafka-streams
apache-kafka-streams
asked Nov 13 at 22:25
Chris
3083416
asked Nov 13 at 22:25
Chris
3083416
asked Nov 13 at 22:25
Chris
3083416
asked Nov 13 at 22:25
Chris
3083416
asked Nov 13 at 22:25
Chris
3083416
3083416
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
stream.process() is a terminal operation in the DSL. You can use stream.transform() instead to get an output stream. A Transformer is basically the same as a Processor.
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.context.forwardwill still be available (it's disadvantage is, that's not type safe; but it works).
– Matthias J. Sax
Nov 14 at 3:59
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
stream.process() is a terminal operation in the DSL. You can use stream.transform() instead to get an output stream. A Transformer is basically the same as a Processor.
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.context.forwardwill still be available (it's disadvantage is, that's not type safe; but it works).
– Matthias J. Sax
Nov 14 at 3:59
add a comment |
up vote
1
down vote
accepted
stream.process() is a terminal operation in the DSL. You can use stream.transform() instead to get an output stream. A Transformer is basically the same as a Processor.
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.context.forwardwill still be available (it's disadvantage is, that's not type safe; but it works).
– Matthias J. Sax
Nov 14 at 3:59
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
stream.process() is a terminal operation in the DSL. You can use stream.transform() instead to get an output stream. A Transformer is basically the same as a Processor.
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
stream.process() is a terminal operation in the DSL. You can use stream.transform() instead to get an output stream. A Transformer is basically the same as a Processor.
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
answered Nov 13 at 23:32
Matthias J. Sax
27.5k34572
27.5k34572
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.context.forwardwill still be available (it's disadvantage is, that's not type safe; but it works).
– Matthias J. Sax
Nov 14 at 3:59
add a comment |
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.context.forwardwill still be available (it's disadvantage is, that's not type safe; but it works).
– Matthias J. Sax
Nov 14 at 3:59
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
With a transformer dont you need to return the value you want to go down stream. In my case I have a context.schedule() that may or may not want to forward content. For your suggestion to work I would need to always have transform() return null and the have context.forward() pass the value to the next operation. Which I dont think will work?
– Chris
Nov 14 at 0:37
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.
context.forward will still be available (it's disadvantage is, that's not type safe; but it works).– Matthias J. Sax
Nov 14 at 3:59
What you say will work. Btw: we are currently adding a "FlatTransformer" to allow you to emit more than one value via return.
context.forward will still be available (it's disadvantage is, that's not type safe; but it works).– Matthias J. Sax
Nov 14 at 3:59
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290440%2fkafka-streams-using-context-forward-from-processor-called-in-dsl-api%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
