Re: [DISCUSS] PIP-208: HTTP Sink

Thanks for your feedback Alexander. My answers to your comments below. BR Christophe Le mer. 21 sept. 2022 à 15:58, Alexander Preuss a écrit : > Hi Christophe, > > I think this is a very good idea! > > I agree with Enrico that the body should depend on the record schema, but > it could also be

Re: [DISCUSS] PIP-208: HTTP Sink

Thanks for your feedback Enrico. My answers to your comments below BR Christophe Le mar. 20 sept. 2022 à 14:16, Enrico Olivelli a écrit : > Christophe, > very good initiative! > > I support it > Some comments inline below > > > Enrico > > Il giorno lun 19 set 2022 alle ore 19:10 Christophe Bor

[GitHub] [pulsar] merlimat added a comment to the discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception

GitHub user merlimat added a comment to the discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception @kyky19831214 You're creating a reader over a partitioned topic. You should create the reader on the individual partitions instead. You can get the list of part

[GitHub] [pulsar] kyky19831214 edited a discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception

GitHub user kyky19831214 edited a discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception the pulsar-client version is 2.9.2, using the same parameter , consumer is ok but reader throws exception when I create them. I change to java creating "reader", that is ok

[GitHub] [pulsar] kyky19831214 added a comment to the discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception

GitHub user kyky19831214 added a comment to the discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception It has been added. GitHub link: https://github.com/apache/pulsar/discussions/17800#discussioncomment-3718005 This is an automatically sent email for de

[GitHub] [pulsar] kyky19831214 edited a discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception

GitHub user kyky19831214 edited a discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception the pulsar-client version is 2.9.2, using the same parameter , consumer is ok but reader throws exception when I create them. I change to java creating "reader", that is ok

Re: CVE-2022-24280: Apache Pulsar Proxy target broker address isn't validated

Please check "Restricting target broker addresses to mitigate CVE-2022-24280" [1] in the Apache Pulsar documentation for more details about configuring the Pulsar Proxy. [1] https://github.com/apache/pulsar/blob/master/site2/docs/administration-proxy.md#restricting-target-broker-addresses-to-m

[GitHub] [pulsar] shibd added a comment to the discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception

GitHub user shibd added a comment to the discussion: python pulsar-clinet create_reader causes "OperationNotSupported" exception @kyky19831214 Hi, Can you provide your reproduce code? GitHub link: https://github.com/apache/pulsar/discussions/17800#discussioncomment-3715895 This is an au

[GitHub] [pulsar] tisonkun edited a discussion: Lightweight Documentation Translation Solution

GitHub user tisonkun edited a discussion: Lightweight Documentation Translation Solution ## Motivation Three years ago we created the [pulsar-translation](https://github.com/apache/pulsar-translation) repository to try to handle documentation translation with Crowdin. However, after three y

[GitHub] [pulsar] raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level.

GitHub user raunakagrawal47 edited a comment on the discussion: Need max redelivery count at message level. @Jason918 Do we need to acknowledge the current message everytime before we send a new message to the retry queue, using reconsumelater()? Else, how will current message get acked and r

[GitHub] [pulsar-helm-chart] yaalsn commented on issue #290: Release Pulsar Helm Chart in GitHub Pages flavor

yaalsn commented on issue #290: URL: https://github.com/apache/pulsar-helm-chart/issues/290#issuecomment-1255883480 IMO, serving `index.yaml` in GitHub page makes sense. 1. This file doesn't need to be visited frequently. 2. Even if GitHub turn down, Github Engs will fix it as soo