Re: [VOTE] PIP-224: Introduce TopicMessageId for consumer's MessageId related APIs

2022-12-10 Thread Enrico Olivelli
+1 (binding) Enrico Il Ven 9 Dic 2022, 10:41 Jiaqi Shen ha scritto: > +1(non-binding) > > Thanks, > Jiaqi Shen > > > 于2022年12月5日周一 15:23写道: > > > +1(non-binding) > > > > Best, > > Mattison > > On Dec 5, 2022, 15:09 +0800, Zike Yang , wrote: > > > +1(non-binding) > > > > > > Best, > > > Zike Ya

[GitHub] [pulsar] devinbost created a discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

2022-12-10 Thread GitBox
GitHub user devinbost created a discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 I have a heartbeat topic that receives messages on the topic `persistent://public/default/canary`, and I configured retention on this topic to test tiered storage in GCP. W

[GitHub] [pulsar] devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

2022-12-10 Thread GitBox
GitHub user devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 FYI @david-streamlio GitHub link: https://github.com/apache/pulsar/discussions/18868#discussioncomment-4369902 This is an automatically sent email for d

[GitHub] [pulsar] devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

2022-12-10 Thread GitBox
GitHub user devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 Could the bucket path be incorrect? Perhaps it doesn't like the prefix. GitHub link: https://github.com/apache/pulsar/discussions/18868#discussioncomment-43699

[GitHub] [pulsar] devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

2022-12-10 Thread GitBox
GitHub user devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 I removed the "gs://" prefix from the bucket name in broker.conf, and the issue was resolved. GitHub link: https://github.com/apache/pulsar/discussions/18868

[GitHub] [pulsar] codelipenghui added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

2022-12-10 Thread GitBox
GitHub user codelipenghui added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 @devinbost Seems we should clarify it in the document, are you interested in fix it? GitHub link: https://github.com/apache/pulsar/discussions/18868#discu

[GitHub] [pulsar] tisonkun added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

2022-12-10 Thread GitBox
GitHub user tisonkun added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 cc @momo-jun This can indicate a doc issue. GitHub link: https://github.com/apache/pulsar/discussions/18868#discussioncomment-4369906 This is an automatic

[GitHub] [pulsar] lhotari created a discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added

2022-12-10 Thread GitBox
GitHub user lhotari created a discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added **Problem** In TLSv1.3, certificates using SHA-1 signature algorithm are considered legacy and it's not recommended that TLSv1.3

[GitHub] [pulsar] tisonkun added a comment to the discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added

2022-12-10 Thread GitBox
GitHub user tisonkun added a comment to the discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added @lhotari what's the status of this issue today? GitHub link: https://github.com/apache/pulsar/discussions/18870#dis

[GitHub] [pulsar] Shoothzj created a discussion: Support report unrecoverable failure warnning by plugin

2022-12-10 Thread GitBox
GitHub user Shoothzj created a discussion: Support report unrecoverable failure warnning by plugin **Is your feature request related to a problem? Please describe.** Sometimes, we are meeting some unrecovered problems. For example, delete zk topic node error, split bundle error **Describe the

[GitHub] [pulsar] Redirts created a discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

2022-12-10 Thread GitBox
GitHub user Redirts created a discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) >From what I understand it is possible to create a custom Java class that reads >from pulsar and writes via JDBC to a database (in my I would like it to be >clickhouse). https://github.com/apac

[GitHub] [pulsar] Redirts added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

2022-12-10 Thread GitBox
GitHub user Redirts added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) Hi, The link you provide describes setting up the jdbc sink without writing any line of code. I would like to be able to manipulate the data before it is sent to clickhouse via java

[GitHub] [pulsar] jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

2022-12-10 Thread GitBox
GitHub user jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) @Redirts is this link help? https://pulsar.apache.org/docs/en/io-quickstart/#connect-pulsar-to-postgresql GitHub link: https://github.com/apache/pulsar/discussions/18872#discussio

[GitHub] [pulsar] tisonkun added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

2022-12-10 Thread GitBox
GitHub user tisonkun added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) @Redirts you can fork and patch the upstream ClickHouse connector for your use case in this situation. GitHub link: https://github.com/apache/pulsar/discussions/18872#discussionco

[GitHub] [pulsar] jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

2022-12-10 Thread GitBox
GitHub user jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) would also like to have @vzhikserg in the thread, who is the author for clickhouse connector. GitHub link: https://github.com/apache/pulsar/discussions/18872#discussioncomment-4369

[GitHub] [pulsar] codelipenghui created a discussion: Throttle the ledger rollover

2022-12-10 Thread GitBox
GitHub user codelipenghui created a discussion: Throttle the ledger rollover **Is your feature request related to a problem? Please describe.** High ledger rollover frequency may lead to zookeeper in heavy workload. In order to make zookeeper run more stable, we should limit the ledger rollover

[GitHub] [pulsar] Jason918 added a comment to the discussion: Throttle the ledger rollover

2022-12-10 Thread GitBox
GitHub user Jason918 added a comment to the discussion: Throttle the ledger rollover @codelipenghui HI, I'll be happy to participate. Please check this more detailed solution. Add a new parameter `managedLedgerRolloverRateLimit`, rate limit the amount of rollover per second in one broker. Thi

[GitHub] [pulsar] EronWright created a discussion: Enable TLS hostname verification by default

2022-12-10 Thread GitBox
GitHub user EronWright created a discussion: Enable TLS hostname verification by default **Is your enhancement request related to a problem? Please describe.** Hostname verification is a critical aspect of TLS, especially when using the system-provided certificate bundle. TLS server authentic

[GitHub] [pulsar] nodece added a comment to the discussion: Enable TLS hostname verification by default

2022-12-10 Thread GitBox
GitHub user nodece added a comment to the discussion: Enable TLS hostname verification by default This idea makes sense, but this change breaks user behavior. GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370029 This is an automatically sent email fo

[GitHub] [pulsar] tisonkun added a comment to the discussion: Enable TLS hostname verification by default

2022-12-10 Thread GitBox
GitHub user tisonkun added a comment to the discussion: Enable TLS hostname verification by default Thanks for your explanation. Then moved to the discussion forum. GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370030 This is an automatically sent em

[GitHub] [pulsar] tisonkun added a comment to the discussion: Enable TLS hostname verification by default

2022-12-10 Thread GitBox
GitHub user tisonkun added a comment to the discussion: Enable TLS hostname verification by default FYI @nodece is this issue still relevant? GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370028 This is an automatically sent email for dev@pulsar.apac

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Enable TLS hostname verification by default

2022-12-10 Thread GitBox
GitHub user codelipenghui added a comment to the discussion: Enable TLS hostname verification by default The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370027 This is an automatically sent

[GitHub] [pulsar] pointearth created a discussion: Pulsar function Should support Generic output Message

2022-12-10 Thread GitBox
GitHub user pointearth created a discussion: Pulsar function Should support Generic output Message **Is your feature request related to a problem? Please describe.** In the pulsar function, I don't want to define a particular class as O in `public interface Function { O process(I var1, Cont

[GitHub] [pulsar] eolivelli added a comment to the discussion: Pulsar function Should support Generic output Message

2022-12-10 Thread GitBox
GitHub user eolivelli added a comment to the discussion: Pulsar function Should support Generic output Message This is related to: https://github.com/apache/pulsar/pull/9590 and to https://github.com/apache/pulsar/pull/9481 I really would like to see this feature land soon. I believe that the

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Pulsar function Should support Generic output Message

2022-12-10 Thread GitBox
GitHub user codelipenghui added a comment to the discussion: Pulsar function Should support Generic output Message The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18875#discussioncomment-4370032 This is an automatic

[GitHub] [pulsar] tisonkun added a comment to the discussion: Pulsar function Should support Generic output Message

2022-12-10 Thread GitBox
GitHub user tisonkun added a comment to the discussion: Pulsar function Should support Generic output Message Move feature "request" to the discussion forum. GitHub link: https://github.com/apache/pulsar/discussions/18875#discussioncomment-4370033 This is an automatically sent email for

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

2022-12-10 Thread GitBox
GitHub user github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18876#discussioncomment-4370053 This is an

[GitHub] [pulsar] ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

2022-12-10 Thread GitBox
GitHub user ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin I also take some attention on this point and I think the current challenge for Pulsar is lacking of the Lua client library like [lua-resty-kafka](https://github.com/doujiang24/lua-r

[GitHub] [pulsar] ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

2022-12-10 Thread GitBox
GitHub user ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin After a brief discuss with @wang-yeliang and @jiazhai, it'll be better to develop the APISIX plugin with native Lua cause of the performance and usability than using the [Plugin Ru

[GitHub] [pulsar] wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

2022-12-10 Thread GitBox
GitHub user wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin We are looking forward to the development of pulsar community friends Lua Pulsar Library and APISIX Pulsar Plugin. Let's enrich the surrounding ecology of Aapche Pulsar. Eric S

[GitHub] [pulsar] wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

2022-12-10 Thread GitBox
GitHub user wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin Maybe I missed the information before. Who developed lua-resty-kafka for Kafka? Eric Shen ***@***.***> 于2021年12月8日周三 20:53写道:

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

2022-12-10 Thread GitBox
GitHub user github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18876#discussioncomment-4370052 This is an

[VOTE] Pulsar Release 2.9.4 Candidate 2

2022-12-10 Thread 丛搏
This is the second release candidate for Apache Pulsar, version 2.9.4. This release contains 317 commits by 69 contributors. https://github.com/apache/pulsar/compare/v2.9.3...v2.9.4-candidate-2 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours ***