GitHub user dhinesherode91 added a comment to the discussion: Cannot parse <null> schema
Thanks for the information. In my case, in my local I am running a standalone Pulsar and Consumer applications are Spring boot application. The above issue is not occurring in local. But in staging and production setups, we are running Pulsar in kubernetes and our Consumer spring boot applications are running as Containers. In those setups I could see this issue more often and I have to restart my containers to make it work. On debugging we could see like the schema is not available in the consumer application pulsar client local cache and due to that on every message receive when the pulsar client tries to convert that respective message into respective class object by parsing the schema, it throws this 'Cannot parse null schema' error. Something related to having/loading SchemaInfo in the memory. It would be great if someone from the team could help us in fixing it. GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414969 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
