Kafka Streams same input and output destination causes already defined error

When I define Function with same input and output bindings, I get bean with that name has already been defined. Using spring-cloud Hoxton.SR1.

application.yml

spring:
  cloud:
    stream:
      function:
        definition: eventStream
        bindings:
          eventStream-in-0:
            destination: events-topic
          eventStream-out-0:
            destination: events-topic

@Bean
public Function<KStream<UUID, Event>, KStream<UUID, Event>> eventStream() {
        return kStream -> kStream
                .map(...);
}

[vitjouda]

@sobychacko We were implementing simple Saga pattern with orchestrator and decided to use one topic for multiple types of messages to ensure sequential processing for all participants in case of failure or lags if it were on multiple topics. Orchestrator logic handles state transitions and ignores whatever might cause any cycles. Clients simply never listen or ignore response types so they never cycle. We bypassed this using .to operator for the moment.

I still think this should work because @StreamListener based handlers can achieve this binding. I will provide simple example as soon as I have some spare time.

[sabbyanandan]

Closing due to no activity.