[GitHub] [pulsar] fmiguelez edited a comment on issue #4803: Pulsar schema doesn't support null value

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

fmiguelez edited a comment on issue #4803:
URL: https://github.com/apache/pulsar/issues/4803#issuecomment-651003387


   The solution provided by #7139 to this BUG **does not work**.
   
   - When trying to read a message with `null` value a `NullPointerException ` is thrown in other part of the code.
   
   ```
           msg = consumer.receive(timeoutMillis, TimeUnit.MILLISECONDS));
   
   	java.lang.NullPointerException
   		at org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl.updateNumMsgsReceived(ConsumerStatsRecorderImpl.java:169)
   		at org.apache.pulsar.client.impl.ConsumerImpl.messageProcessed(ConsumerImpl.java:1423)
   		at org.apache.pulsar.client.impl.ConsumerImpl.internalReceive(ConsumerImpl.java:431)
   		at org.apache.pulsar.client.impl.ConsumerBase.receive(ConsumerBase.java:175)
                   ...
   ```
   - It should not be required to explicitly indicate a `null `value to producer (only-key values should work just just fine). Exception thrown when working with implicit null value messages is `EOFException `in this case (the same before this a solution was provided).
   
   I have created a test project to reproduce these issues (null values implicitly and explictly set with both schema and schemaless consumer): [pulsar-tombstone-test](https://github.com/fmiguelez/pulsar-tombstone-test)
   
   
   
   
   
   


----------------------------------------------------------------
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.

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