[GitHub] [pulsar] Raven888888 commented on issue #12284: Pulsar SQL BufferUnderflowException after upgrading from 2.7.0 to 2.8.1

[GitBox <gi...@apache.org>]

Raven888888 commented on issue #12284:
URL: https://github.com/apache/pulsar/issues/12284#issuecomment-1117489085

   @gaoran10 Sorry to say but the issue I faced still persists.
   
   I recently only have the time to try your PR #12809 . I used the official 2.10.0 binary, which should already contain your PR, and did a clean install.
   
   However, I still face the exact same `BufferUnderflowException` error (and same error log) when I
   1. use websocket client to produce a message *without schema* to a topic
   2. upload `string` schema to the topic (`conf/schema_example.conf`)
   3. face the error when query from pulsar SQL
   
   Note that:
   - I use the default settings in `broker.conf`, not sure if they play a role here. Some of the paramaters are added after pulsar 2.7.0, which leads me to relate that this `BufferUnderflowException` did NOT happen in pulsar 2.7.0 before...
   ```
   isAllowAutoUpdateSchemaEnabled=true
   systemTopicSchemaCompatibilityStrategy=ALWAYS_COMPATIBLE
   topicLevelPoliciesEnabled=false
   isSchemaValidationEnforced=false
   schemaCompatibilityStrategy=FULL
   ```
   - I understand that using a pulsar client that supports producing schema, can solve the issue. However, **this requires changes on client side and is unfortunately not possible**. I'd like a solution on the server side.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org