Baodi Shi
Baodi Shi
@jianyun8023 @syhily Can you help me review the way to solve the problem?
> @shibd @jianyun8023 Since the MR for pulsar is too slow to be merged. I think we may need a workaround on the connector side. I think connector need support...
The producer of DLQ should be a low-frequency operation, and we can turn off batch sending by default, just like the Java client behaves. And there's no need to expose...
Close this issue, it solves by cpp3.5.0, and the node.js client has already upgraded it.
@dao-jun Can you resolve the conflict and add a unit test?
hi, @tjiuming Thanks for your PR. Maybe we can change this test to cover all related transactions get lastmessage id case. https://github.com/apache/pulsar/blob/a761b97b733142b1ade525e1d1c06785e98face1/pulsar-broker/src/test/java/org/apache/pulsar/broker/transaction/buffer/TopicTransactionBufferTest.java#L264 Change to: ```java @Test public void testGetLastMessageIdsWithOngoingTransactions() throws...
> @codelipenghui @shibd @coderzc It looks like Shared/key_Shared Consumer also could be stuck from delayed delivery messages, WDYT? Do we need to handle it? I prefer case by case fix...
After version 1.8.0, you can easily use this command to install to windows systems: `npm install [email protected]`, and you no longer need to install the CPP client first.
Now, you can install Node.js client by use flow cmd: ``` npm install pulsar-client ```