[GitHub] [pulsar] tisonkun commented on issue #20092: [Bug] Pulsar client AUTO_CONSUME "double" as "BigDecimal" in JSON schemas

tisonkun commented on issue #20092: URL: https://github.com/apache/pulsar/issues/20092#issuecomment-1508322846 I create a patch to fix your use case https://github.com/apache/pulsar/pull/20104. You can give it a try and help in review. I don't know if it affects other use case but

[GitHub] [pulsar] tisonkun commented on issue #20092: [Bug] Pulsar client AUTO_CONSUME "double" as "BigDecimal" in JSON schemas

tisonkun commented on issue #20092: URL: https://github.com/apache/pulsar/issues/20092#issuecomment-1508264901 Basically I don't think it's bad but we should adjust to correct schema using schema info. -- This is an automated message from the Apache Git Service. To respond to the

[GitHub] [pulsar] tisonkun commented on issue #20092: [Bug] Pulsar client AUTO_CONSUME "double" as "BigDecimal" in JSON schemas

tisonkun commented on issue #20092: URL: https://github.com/apache/pulsar/issues/20092#issuecomment-1508264050 I think it's this PR change the behavior: https://github.com/apache/pulsar/pull/15687 Note that we now use: ```

[GitHub] [pulsar] tisonkun commented on issue #20092: [Bug] Pulsar client AUTO_CONSUME "double" as "BigDecimal" in JSON schemas

tisonkun commented on issue #20092: URL: https://github.com/apache/pulsar/issues/20092#issuecomment-1508233139 Thanks for your report @aymkhalil! Can you try out 2.11.0 and build from source? I cannot reproduce this issue with current master 091ee2504ffbe6ec98e354b76e7f4c045e1914aa. --