Closed aymkhalil closed 1 year ago
@eolivelli
maxPendingMessage
is configured on the producer and has default value alreadymemoryLimit
that is disabled by default anyway. maxPendingMessagesAcrossPartitions
is deprecated and I think it is better to drop it as I don't expect future support for itPTAL.
Behavior of the JsonNode node returned in the NativeObject has changes. I have to tests failing now with:
java.lang.AssertionError: Wrong value for regular field double expected:<1.0> but was:<1>
With 2.8.3, I would get "1.0" when accessing node.numberValue()
with DOUBEL schema. Now I get an "1" integer.
Need to troubleshoot further...
Update: Regression was introduced in 2.10.1. I captured the issue here https://github.com/apache/pulsar/issues/20092
In the mean time, I downgraded the client in the tests to 2.8.3 (like it was before). This Patch is still meaning full because it successfully update the client on the agent side to 2.10.3 and the connector client is only used in the integration tests.
2.8 has performance reported issue, recommended to update to 2.10.x. Please note that the connector pulsar client will be vended by the environment, but this upgrade benefits the agent. It also unified the client version between the Agent and CLI tool.
Notes: