title: Not able to write AVRO object to another topic using kafka streams
body: <p>I have a kafka streams app, which reads an AVRO message do some transformation on it and then write it to another topic. I can able to read AVRO message without any issues but while writing to another topic, I am getting the following error. This particular error code is nowhere found in the internet.</p>
  
  <blockquote>
    <p>Caused by: org.apache.kafka.common.errors.SerializationException: Error registering Avro schema: {"type":"record","name":"Value","namespace":"com.github.jcustenborder.kafka.connect.model","fields":[{"name":"StoreId","type":["null","string"],"default":null},{"name":"TransactionId","type":["null","string"],"default":null},{"name":"TransactiontimestampArchivo","type":["null","string"],"default":null},{"name":"Transactiontimestamp","type":["null","string"],"default":null},{"name":"Itembarcode","type":["null","string"],"default":null},{"name":"Iteminternalcode","type":["null","string"],"default":null},{"name":"Itemdescription","type":["null","string"],"default":null},{"name":"Itemsalevolume","type":["null","string"],"default":null},{"name":"Itemunitprice","type":["null","string"],"default":null},{"name":"Itemtotalsale","type":["null","string"],"default":null},{"name":"Transactiontotalsale","type":["null","string"],"default":null},{"name":"ItemCategory","type":["null","string"],"default":null},{"name":"IsWeight","type":["null","string"],"default":null}],"connect.name":"com.github.jcustenborder.kafka.connect.model.Value"}
    Caused by: io.confluent.kafka.schemaregistry.client.rest.exceptions.RestClientException: Unexpected character ('&lt;' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')</p>
  </blockquote>
  
  <p>Here is <a href="https://github.com/Landoop/stream-reactor/issues/148" rel="nofollow noreferrer">a thread</a> which talks about the very same error code, but someone concluded the thread relates this issue with Authentication. Currently the schema registry that we are running, we haven't secured it. It is a plain dev server with no such security.</p>