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

fmiguelez commented on issue #4803: URL: https://github.com/apache/pulsar/issues/4803#issuecomment-652252521 @gaoran10, @jiazhai I have opened a new ticket #7407 as indicated This is an automated message from the Apache Git S

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

fmiguelez commented on issue #4803: URL: https://github.com/apache/pulsar/issues/4803#issuecomment-651019393 > Thanks @fmiguelez for the test. > looks from the code, npe happens in stats path(ConsumerStatsRecorderImpl.java), would you like to provide a pull request to fix this issue:

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

fmiguelez commented on issue #4803: URL: https://github.com/apache/pulsar/issues/4803#issuecomment-651003387 The solution provided by solution #7139 to this BUG **does not work**. - When trying to read a message with `null` value a `NullPointerException ` is thrown in other part of t

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

fmiguelez commented on issue #4803: URL: https://github.com/apache/pulsar/issues/4803#issuecomment-625317625 There is a workaround with direct consumer/reader interface since you can always verify if data is empty before calling getValue(): Message lastMsg = reader.readNext(); lastEn