-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Invalid data in message: Message failed schema validation. #272
Comments
We will need more details to be able to look into this for you - specifically we will need to look at the Pub/Sub topic schema and the sample message you are trying to send. If your schema/data is confidential, you can try to reproduce the error with non-confidential data. |
I run into similar issue. I have a avro schema for my kafka topic. I created the same schema for my pubsub topic (copied the schema from my kafka schema registry and used it as gcp pubsub schema for the pubsub topic). I tested the same message that is in the kafka topic directly by copying the same message and publish the message in gcp pubsub topic by using the gcp web console and the message is published.
Avro schema:
Stacktrace: I have tested the connector and it is sinking the data into pubsub topic when pubsub topic does not use any schema. However, the kafka message payload is not stored in the Message Body(pubsub topic), rather all the fields in the message payload is exploded as attribute. . @samarthsingal looking forward to your feedback! |
I have tested for a simple avro schema that I created for both my new test kafka topic and pubsub topic that is as follows:
I have validated the pubsub topic schema for following message payload that is validated successfully:
But getting the same Schema validation error in my sink connector |
I have this Kafka topic named
source
which contains AVRO messages already derived from the schema registry onhttp://localhost:9080
. Producing the messages was as (see code below) to which the messages can be viewed by the Kafka UI (through the schema registry), hence (as I believe) the schema registry is also working as expected.However, when I am setting up a Sink PubSub Connector from the
source
topic tocps.topic.test
using the connector below. Am getting these stacktraceConnector config
Error
What seems to be the issue why am getting the error message?
The text was updated successfully, but these errors were encountered: