Re: [DISSCUSS] PIP-325: Add command to abort transaction
Hi, Ruihong This proposal looks good to me. BR, Xiangying On Tue, Dec 19, 2023 at 8:13 PM Xiangying Meng wrote: > Hi, Ruihong > > Thanks for your proposal. > I wonder whether we should abort all the transactions one client creates > when the client crushes. > For example, a process builds a Pulsar client and creates a transaction by > this client to do some operations. > If the process crushes, the transaction cannot be committed or aborted. > > In this case, aborting the transaction automatically when the client is > crushed may be more helpful than aborting them after restarting. > > BR, > Xiangying > > > On Mon, Dec 18, 2023 at 9:08 AM PengHui Li wrote: > >> Hi, Ruihong >> >> The proposal looks good to me. >> Just left a comment about the security considerations. >> We need to have a clear permission definition for newly added admin API >> >> Regards, >> Penghui >> >> On Sun, Dec 17, 2023 at 1:14 AM |海阔天高 <1373544...@qq.com.invalid> wrote: >> >> > Hi community, >> > >> > >> > PIP-325 introduces a new API for aborting transactions, allowing >> > administrators to proactively abort a transaction when it gets stuck, >> thus >> > preventing consumers from being blocked for an extended period. >> > >> > >> > Hopes for discuss. >> > PIP: https://github.com/apache/pulsar/pull/21731 >> > Releted PR: https://github.com/apache/pulsar/pull/21630 >> > >> > >> > Thanks, >> > >> > >> > Ruihong >> > >> > >> > |海阔天高 >> > 1373544...@qq.com >> > >> > >> > >> > >> >
Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it
Since there seems to be agreement here, I'll proceed with the PR for removing the code. If there are volunteers that are willing to continue maintaining the Trino plugin, I'll be happy to help out in setting up the new repository and import the existing code. Thanks, Matteo -- Matteo Merli On Sun, Dec 24, 2023 at 7:47 PM Yubiao Feng wrote: > +1 > > Thanks > Yubiao Feng > > On Sat, Dec 23, 2023 at 1:09 AM Matteo Merli wrote: > > > I want to start a discussion regarding the removal of all the code > related > > to the Trino (PrestoDB) plugin from the Pulsar main repository. > > > > This topic was already discussed and approved long time ago in PIP-62 ( > > > > > https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories > > ) > > > > The main reasons for not having Presto plugin as part of the main > > distribution of Pulsar were (and still are valid): > > > > 1. We need to ship the entire Presto runtime which is ~400 MB. This > makes > > our tgz and Docker images huge > > 3. There is no strict need for this component to be in the same > > distribution / image: it could easily be provided in a different release > > tgz or Docker image > > > > Though I think that since then it became more clear that the current > state > > of this plugin has been stagnating over the years. > > > > 1. There are not many active users of Pulsar-SQL component (I'd be very > > happy to be contradicted here) > > 2. The plugin code has not been improved in a long time > > 3. There are several open security issues (actually, almost the totality > of > > current dependencies issues are today coming from Trino). > > > > My suggestion would be that, if there is any volunteer willing to pick > this > > plugin up and maintain it in a separate repository (within the Apache > > Pulsar project) and with a separate release schedule, we should go ahead > > and move it. > > If there are no volunteers, we should just remove it as it is. If later > on > > we want to revive it, we can always import the code from the last commit. > > > > Thoughts? > > > > > > -- > > Matteo Merli > > > > >
Re: [VOTE] Pulsar Release 3.1.2 Candidate 2
bump Enrico Olivelli 于2023年12月18日周一 21:21写道： > +1 (binding) > > Built from sources > Run some smoke tests with Pulsar standalone > Verified checksums and signatures (I had to import KEYS, there was a new > key) > > Enrico > > Il giorno mer 13 dic 2023 alle ore 09:42 guo jiwei > ha scritto: > > > > +1 (binding) > > > > - Checked the signatures > > - Built from source > > - Run standalone and check the produce, consume > > - Verified Cassandra connector > > - Verified stateful function > > > > > > Regards > > Jiwei Guo (Tboy) > > > > > > On Sat, Dec 9, 2023 at 2:48 PM houxiaoyu wrote: > > > > > This is the second release candidate for Apache Pulsar version 3.1.2. > > > > > > It fixes the following issues: > > > > > > > https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.1+ > > > > > > *** Please download, test and vote on this release. This vote will > > > stay open for at least 72 hours *** > > > > > > Note that we are voting upon the source (tag), binaries are provided > > > for convenience. > > > > > > Source and binary files: > > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.2-candidate-2/ > > > > > > SHA-512 checksums: > > > > > > apache-pulsar-3.1.2-bin.tar.gz > > > > > > > 48e2d0069cd69c6f2bf5b5d5aa9fbc775436d3e160bd51645a6626fb86706ddba4901a5d6b87e29a57b9f19c0d0b8c22aef2dfa3d3525260ad55d0a39db6 > > > > > > apache-pulsar-3.1.2-src.tar.gz > > > > > > > 4d29b1f707047d1bd55d8cb8aacb488517fbd82903fef57c9924180b62454725bdbdc53adf7af5d5caa4d57522a10d6eb15028fd929325b9cadd088a6e3de20a > > > > > > Maven staging repo: > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1256/ > > > > > > The tag to verify: > > > v3.1.2-candidate-2 (c4196fba3ae107d74f9421d3f7ed11c0c245f10f) > > > https://github.com/apache/pulsar/releases/tag/v3.1.2-candidate-2 > > > > > > Pulsar's KEYS file containing PGP keys you use to sign the release: > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > Docker images: > > > > > > pulsar images: > > > https://hub.docker.com/repository/docker/anonhxygo/pulsar > > > > > > pulsar-all images: > > > https://hub.docker.com/repository/docker/anonhxygo/pulsar-all > > > > > > Please download the source package, and follow the README to build > > > and run the Pulsar standalone service. > > > > > > > > > Regards > > > Xiaoyu Hou > > > >
Re: [VOTE] Pulsar Release 2.11.3 Candidate 2
+1 (binding) - Checked the signatures - Built from source - Run standalone and check the produce, consume - Verified Cassandra connector - Verified stateful function Regards Jiwei Guo (Tboy) On Thu, Dec 21, 2023 at 9:32 AM Baodi Shi wrote: > This is the second release candidate for Apache Pulsar, version 2.11.3. > > It fixes the following issues: > > https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.11.3+is%3Aclosed > > *** Please download, test and vote on this release. This vote will stay > open for at least 72 hours *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.11.3-candidate-2/ > > SHA-512 checksums: > > > 521316ea9f01b54f0fb3981dc017d3529de4019360c57c38c72c1ecfa53030927b93608acd71d0eb58f3e7eb6b4a2583a94796462d577d7dca0ba935a2f68fcf > ./apache-pulsar-2.11.3-bin.tar.gz > > > 4510c16d6ec90847eb8dff0246bd09190f99bc10a30702ab5f521971b13b6cffe0f9d1de9637b85340154ee38764a39551fd871bd1132d7760fb3a7e931a20e3 > ./apache-pulsar-2.11.3-src.tar.gz > > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1258/ > > The tag to be voted upon: > v2.11.3-candidate-2 (c7ac62c > < > https://github.com/apache/pulsar/commit/c7ac62ca9eb718e15c3e3e4a460167643ef3f48b > > > ) > https://github.com/apache/pulsar/releases/tag/v2.11.3-candidate-2 > > Pulsar’s KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Docker images: > docker pull wudixiaobaozi/pulsar-all:2.11.3 > docker pull wudixiaobaozi/pulsar:2.11.3 > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. > > Thanks, > Baodi Shi >
Re: [DISCUSS] PIP-328: Add a topicDeleteProtectionEnable configuration option.
Hi Jie Maybe a limitation of Authorization permissions is better? Thanks Yubiao Feng On Mon, Dec 25, 2023 at 7:05 PM Jie crossover wrote: > Hi dev, > I proposed a PIP: https://github.com/apache/pulsar/pull/21800 > to avoid mistaken data deletion. > Please take a look and give your feedback. > -- > Best Regards！ > crossoverJie >
[DISCUSS] PIP-328: Add a topicDeleteProtectionEnable configuration option.
Hi dev, I proposed a PIP: https://github.com/apache/pulsar/pull/21800 to avoid mistaken data deletion. Please take a look and give your feedback. -- Best Regards！ crossoverJie
Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters
Hi Xiangying In my test, the topic-level replication works as expected when using a different configuration metadata store but can not work as expected when using the same configuration metadata store. I have two questions: - Do any exact users use the global config metadata store and still need topic-level replication? - There is a prop `allowed_clusters` on the tenant level and a prop `replicated_clusters` on the namespace level. Is it possible that `replicated_clusters` is designed for Replication but incorrectly used to do a permission check? If yes, can we just remove this permission check? Thanks Yubiao Feng On Thu, Nov 30, 2023 at 1:26 PM Xiangying Meng wrote: > Hi, Pulsar Community > > I drafted a proposal to make the configuration of clusters at the namespace > level clearer. This helps solve the problem of geo-replication not working > correctly at the topic level. > > https://github.com/apache/pulsar/pull/21648 > > I'm looking forward to hearing from you. > > BR > Xiangying >
