anchor.diff:  To avoid any conflicts in the future, starting with 1.1.1.RELEASE, we have opted for the name `SCHEMA_REPOSITORY` for the storage table.
   Any Spring Cloud Stream 1.1.0.RELEASE users who upgrade should migrate their existing schemas to the new table before upgrading.
   
  -=== Schema Registry Client
  -
  -The client-side abstraction for interacting with schema registry servers is the `SchemaRegistryClient` interface, which has the following structure:
  -
  -[source,java]
  -----
  -public interface SchemaRegistryClient {
  -
  -    SchemaRegistrationResponse register(String subject, String format, String schema);
  -
  -    String fetch(SchemaReference schemaReference);
  -
  -    String fetch(Integer id);
  -
  -}
  -----
  -
  -Spring Cloud Stream provides out-of-the-box implementations for interacting with its own schema server and for interacting with the Confluent Schema Registry.
  -
  -A client for the Spring Cloud Stream schema registry can be configured byusing the `@EnableSchemaRegistryClient`, as follows:
  -
  -[source,java]
  -----
  -  @EnableBinding(Sink.class)
  -  @SpringBootApplication
  -  @EnableSchemaRegistryClient
  -  public static class AvroSinkApplication {
  -    ...
  -  }
  -----
  -
  -NOTE: The default converter is optimized to cache not only the schemas from the remote server but also the `parse()` and `toString()` methods, which are quite expensive.
  -Because of this, it uses a `DefaultSchemaRegistryClient` that does not caches responses.
  -If you intend to use the client directly on your code, you can request a bean that also caches responses to be created.
  -To do so, add the property `spring.cloud.stream.schemaRegistryClient.cached=true` to your application properties.
  -
   ==== Using Confluent's Schema Registry
   
   The default configuration creates a `DefaultSchemaRegistryClient` bean.
  
positive.code: [[schema-evolution]]
  == Schema Evolution Support
  
  Spring Cloud Stream provides support for schema-based message converters through its `spring-cloud-stream-schema` module.
  Currently, the only serialization format supported out of the box for schema-based message converters is Apache Avro, with more formats to be added in future versions.
  
  === Apache Avro Message Converters
  
  The `spring-cloud-stream-schema` module contains two types of message converters that can be used for Apache Avro serialization:
  
  * Converters that use the class information of the serialized or deserialized objects or a schema with a location known at startup.
  
negative.code:   }
  }
  ----
  
  === Schema Registry Server
  
  