I figured it out.  The value of field "schem" is just a string so I needed to 
escape my JSON:

{
    "schema":"{\"type\": \"record\",\"name\": \"GenericAuditRecord\", 
\"fields\": [{ \"name\": \"xml\",\"type\": [\"string\", \"null\"] }]}"
}

-Dave


-----Original Message-----
From: Dustin Cote [mailto:dus...@confluent.io]
Sent: Monday, June 13, 2016 11:36 AM
To: users@kafka.apache.org
Subject: Re: Schema Registry Exception

Hi Dave,

This looks like invalid JSON.  I see an extra comma in the fields stanza.
Maybe you can try with this (below)?

{
"schema": {
"type": "record",
"name": "GenericAuditRecord",
"fields": [{
"name": "xml",
"type": ["string", "null"]
}]
}
}



On Mon, Jun 13, 2016 at 8:38 AM, Tauzell, Dave <dave.tauz...@surescripts.com
> wrote:

> I'm getting the following exception when trying to register a schema:
>
>
> [2016-06-13 11:37:14,531] INFO 172.23.147.101 - -
> [13/Jun/2016:11:37:14 -0400] "POST
> /subjects/GenericAuditRecord/versions HTTP/1.1" 500 52  7
> (io.confluent.rest-utils.requests:77)
> [2016-06-13 11:38:31,292] ERROR Unhandled exception resulting in
> internal server error response
> (io.confluent.rest.exceptions.GenericExceptionMapper:37)
> com.fasterxml.jackson.databind.JsonMappingException: Can not
> deserialize instance of java.lang.String out of START_OBJECT token at
> [Source:
> org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnClos
> eableInputStream@726bacc9;
> line: 2, column: 5] (through reference chain:
> io.confluent.kafka.schemaregistry.client.rest.entities.requests.Regist
> erSchemaRequest["schema"])
>
> I am posting this:
>
> {
>     "schema": {
>                         "type": "record",
>                         "name": "GenericAuditRecord",
>                         "fields": [
>                                                             {"name":
> "xml", "type": ["string", "null"]},
>                                                          ]
>         }
> }
>
> Any ideas as to what I am doing wrong?
>
> -Dave
>
> This e-mail and any files transmitted with it are confidential, may
> contain sensitive information, and are intended solely for the use of
> the individual or entity to whom they are addressed. If you have
> received this e-mail in error, please notify the sender by reply
> e-mail immediately and destroy all copies of the e-mail and any attachments.
>



--
Dustin Cote
confluent.io
This e-mail and any files transmitted with it are confidential, may contain 
sensitive information, and are intended solely for the use of the individual or 
entity to whom they are addressed. If you have received this e-mail in error, 
please notify the sender by reply e-mail immediately and destroy all copies of 
the e-mail and any attachments.

Reply via email to