2020-09-24 13:27:35 UTC - Ravi Shah: Hi Guys, I can see there is a support for unsubscribe method in Github repo for Node.js which is not released in 1.2.0 version on NPM.
Is there any ETA for this to be released and available? ---- 2020-09-24 17:33:39 UTC - Evan Furman: I don’t see `/pulsar-manager/pulsar-manager/application.properties` in the container. Assuming if I create one it’ll get read on startup? ```/pulsar-manager # ls entrypoint.sh init_db.sql pulsar-manager pulsar-manager.log startup.sh supervisor.sock supervisord.log supervisord.pid /pulsar-manager # cd pulsar-manager/ /pulsar-manager/pulsar-manager # ls bin lib``` ---- 2020-09-24 17:34:04 UTC - Addison Higham: what version of the image are you using? ---- 2020-09-24 17:34:25 UTC - Addison Higham: that was in `apachepulsar/pulsar-manager:v0.2.0` ---- 2020-09-24 17:35:15 UTC - Addison Higham: ah yes, it looks like that was added in `v0.2.0` ---- 2020-09-24 17:35:28 UTC - Evan Furman: Ah, yep, I see the updated image on dockerhub. The docs still reference v0.1.0 ---- 2020-09-24 17:44:58 UTC - Lari Hotari: @Penghui Li great that there's already a plan. please also take a look at <https://github.com/apache/pulsar/issues/6869|https://github.com/apache/pulsar/issues/6869> . When I filed the bug there was also a case that calling org.apache.pulsar.client.api.Consumer#negativeAcknowledge(org.apache.pulsar.client.api.MessageId) doesn't remove the message id from the underlying UnAckedMessageTracker when the message is instance of BatchMessageIdImpl. ---- 2020-09-24 17:48:24 UTC - Sijie Guo: @Nozomi Kurihara ^ ---- 2020-09-24 17:54:53 UTC - Evan Furman: Does `bookie_host` need to be a list of the bookie nodes? ---- 2020-09-24 17:55:53 UTC - Sijie Guo: No it doesn’t ---- 2020-09-24 17:56:10 UTC - Sijie Guo: You can just connect to any bookie. If you have a DNS for the bookie cluster, you can use that. ---- 2020-09-24 17:56:24 UTC - Evan Furman: awesome, ok testing now ---- 2020-09-24 18:55:01 UTC - Sijie Guo: If you are looking an instructor-led Pulsar developer training, we will host a 2-days (4 half-days) Pulsar training session with Jesse Anderson on October 12-15. Reserve you seats. You can also reach out to me for discounts if you will have more people to attend the training session. <https://www.eventbrite.com/e/developing-pulsar-applications-online-training-tickets-122334542911> ---- 2020-09-24 20:43:52 UTC - Andy Papia: I have a use case for delayed message delivery. I found this: <https://github.com/apache/pulsar/wiki/PIP-26:-Delayed-Message-Delivery> and this: <https://github.com/apache/pulsar/issues/2375> ---- 2020-09-24 20:44:48 UTC - Andy Papia: Does anyone know if this is currently a supported use case? Seems like maybe the elegant solution proposed in the PIP is not implemented yet but maybe it is still supported based on the work in issue #2375? ---- 2020-09-24 20:46:42 UTC - Addison Higham: It is included as of pulsar 2.4.0, see <https://pulsar.apache.org/blog/2019/07/05/Apache-Pulsar-2-4-0/#delayed-message-delivery> Or is there something more specific you are looking for? ---- 2020-09-24 20:47:44 UTC - Andy Papia: oh perfect! that's what I wanted to hear. didn't look like it wasn't supported yet based on the status of PIP-26. ---- 2020-09-24 21:57:08 UTC - Evan Furman: ok I ended up baking our own container and copying in the `application.properties` file. However, it doesn’t seem like the default creds work: ```# If user.management.enable is true, the following account and password will no longer be valid. pulsar-manager.account=pulsar pulsar-manager.password=pulsar # If true, the database is used for user management user.management.enable=false``` ---- 2020-09-24 21:57:41 UTC - Evan Furman: Note, I set `user.management.enable` to `false` ---- 2020-09-24 21:58:23 UTC - Evan Furman: ---- 2020-09-25 00:52:52 UTC - Nozomi Kurihara: @Ravi Shah Hi, we're planning the next release of node.js client in November, 2020. ---- 2020-09-25 04:44:01 UTC - Ravi Shah: Thanks ---- 2020-09-25 06:34:35 UTC - Maor Goaz: @Maor Goaz has joined the channel ---- 2020-09-25 07:32:58 UTC - Lei Li: @Lei Li has joined the channel ---- 2020-09-25 08:07:46 UTC - Gabriel Ciuloaica: @Gabriel Ciuloaica has joined the channel ---- 2020-09-25 08:47:38 UTC - Rahul Vashishth: Unable to create producer for auth enabled pulsar cluster. `client.newProducer` always times out. ```PulsarClient client = PulsarClient.builder() .serviceUrl(SERVICE_URL) .authentication("our.custom.idp.pulsar.client.AuthenticationTokenIdx", "token:my_jwt_token") .build(); Producer<byte[]> producer = client.newProducer() .topic(TOPIC2) .compressionType(CompressionType.LZ4).create();``` While i am able to produce message using toolset pod, after chaining the conf/client.conf file on the same cluster/topic. After editing the below ```authPlugin=our.custom.idp.pulsar.client.AuthenticationTokenIdx authParams=token:my_jwt_token``` please suggest if i am passing the `authParamsString` with right key for jwt token, in the `.authentication(authPluginClassname,authParamsString)` ----
