This message was deleted.

Does the topic in question already exist, or are you expecting it to be auto-created when you produce the messages? if the former, it has a schema associated with it, and you must either publish messages that conform to that schema or disable schema enforcement on the topic.

Yes, it's the former. The error messages and the examples I see for other clients seem to indicate that the client needs to know the schema somehow, not just have the message conform. But maybe I'm mistaken? Here's the schema if it helps:

{
  "type": "record",
  "name": "enum_test_schema",
  "namespace": "default",
  "fields": [
    {
      "name": "color",
      "type": {
        "type": "enum",
        "name": "Color",
        "symbols": [
          "unknown",
          "green",
          "red"
        ]
      },
      "default": "unknown"
    }
  ]
}

Got it. So you are interested in how to publish schema’ed messages from the command line, is that correct?

yes

You can use the

--value-schema

flag on the produce command to specify JSON, AVRO, String, or bytes. Then pass in a compatible payload for the message

I tried that flag and it errors on

AVRO

,

avro

,

JSON

,

json

, etc

Does enclosing AVRO in quotes make a difference? “AVRO”, or ‘AVRO’ ?

nope, same thing

Which client version are you using?

I grabbed it from Datastax over here: https://github.com/datastax/homebrew-luna-streaming-shell/tree/master

No problem. FWIW, given the recent departures within the Pulsar team at DataStax, you might want to avoid their tooling, as the maintenance/updates on those might be lacking going forward.

Ok, thanks for the heads up. I'm trying to duplicate a customer issue so not thinking too hard about tooling at the moment.