anchor.diff:  You need to disable native encoding for all the output individually in the case of branching. Otherwise, native encoding will still be applied for those you don't disable.
   
   When conversion is done by Spring Cloud Stream, by default, it will use `application/json` as the content type and use an appropriate json message converter.
  -You can use custom message converters by using the following property.
  +You can use custom message converters by using the following property and a corresponding `MessageConverter` bean.
   ```
   spring.cloud.stream.bindings.process-out-0.contentType
   ```
  
positive.code: 
  Note: Using `resetOffsets` on the consumer does not have any effect on Kafka Streams binder.
  Unlike the message channel based binder, Kafka Streams binder does not seek to beginning or end on demand.
  
  === Accessing the underlying KafkaStreams object
  
  `StreamBuilderFactoryBean` from spring-kafka that is responsible for constructing the `KafkaStreams` object can be accessed programmatically.
  Each `StreamBuilderFactoryBean` is registered as `stream-builder` and appended with the `StreamListener` method name.
  If your `StreamListener` method is named as `process` for example, the stream builder bean is named as `stream-builder-process`.
  Since this is a factory bean, it should be accessed by prepending an ampersand (`&`) when accessing it programmatically.
  Following is an example and it assumes the `StreamListener` method is named as `process`
  
  [source]
  ----
  StreamsBuilderFactoryBean streamsBuilderFactoryBean = context.getBean("&stream-builder-process", StreamsBuilderFactoryBean.class);
  			KafkaStreams kafkaStreams = streamsBuilderFactoryBean.getKafkaStreams();
  ----
negative.code: 
  Spring Cloud Stream will ensure that the messages from both the incoming and outgoing topics are automatically bound as
  KStream objects. As a developer, you can exclusively focus on the business aspects of the code, i.e. writing the logic
  required in the processor. Setting up Kafka Streams specific configuration required by the Kafka Streams infrastructure
  is automatically handled by the framework.
  
  The two examples we saw above have a single `KStream` input binding. In both cases, the bindings received the records from a single topic.
  