You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by JiangHaiting <ji...@foxmail.com> on 2021/09/28 14:04:49 UTC
[PIP 100] Add seekByIndex for consumer api
Hi Pulsar Community,
I'm glad to have this opportunity to propose this PIP.
Currently we can reset the read position of a cursor by message id or timestamp.
Since we formerly introduced index in broker metadata since 2.9.0,
reset cursor by index is very helpful in other protocol handler (KoP or RoP).
Also, as @BewareMyPower pointed out that
"users might want to seek to 10000 messages before. Currently they cannot achieve this goal.".
And this PIP will make it possible.
I've already created a PR, see details at https://github.com/apache/pulsar/pull/12032
Thanks,
Haiting Jiang (Github:Jason918)
Re: [PIP 100] Add seekByIndex for consumer api
Posted by JiangHaiting <ji...@foxmail.com>.
Hi Yunze,
Thanks for the reminding.
I will come up with the issue and new mail for this pip.
------------------ Original ------------------
From: "dev" <yzxu@streamnative.io.INVALID>;
Date: Tue, Sep 28, 2021 10:13 PM
To: "dev"<dev@pulsar.apache.org>;
Subject: Re: [PIP 100] Add seekByIndex for consumer api
You need to create an issue first to start a discussion for your PIP.
Here’s the process of PIP:
1. The author(s) of the proposal will create a GitHub issue ticket choosing the
template for PIP proposals.
2. The author(s) will send a note to the dev@pulsar.apache.org <mailto:dev@pulsar.apache.org> mailing list
to start the discussion, using subject prefix `[PIP] xxx`.
3. Based on the discussion and feedback, some changes might be applied by
authors to the text of the proposal.
4. Once some consensus is reached, there will be a vote to formally approve
the proposal.
The vote will be held on the dev@pulsar.apache.org <mailto:dev@pulsar.apache.org> mailing list. Everyone
is welcome to vote on the proposal, though it will considered to be binding
only the vote of PMC members.
I would be required to have a lazy majority of at least 3 binding +1s votes.
The vote should stay open for at least 48 hours.
5. When the vote is closed, if the outcome is positive, the state of the
proposal is updated and the Pull Requests associated with this proposal can
start to get merged into the master branch.
Thanks,
Yunze
> 2021年9月28日 下午10:04，JiangHaiting <jianghaiting@foxmail.com> 写道：
>
> Hi Pulsar Community,
>
>
> I'm glad to have this opportunity to propose this PIP.
>
>
> Currently we can reset the read position of a cursor by message id or timestamp.&nbsp;
> Since we formerly introduced index in broker metadata since 2.9.0,&nbsp;
> reset cursor by index is very helpful in other protocol handler (KoP or RoP).
>
>
> Also, as @BewareMyPower pointed out that&nbsp;
> "users might want to seek to 10000 messages before. Currently they cannot achieve this goal.".&nbsp;
> And this PIP will make it possible.
>
>
> I've already created a PR, see details at https://github.com/apache/pulsar/pull/12032
>
>
>
> Thanks,
> Haiting&nbsp;Jiang (Github:Jason918)
---
Thanks,
Haiting Jiang (Github: Jason918)
Re: [PIP 100] Add seekByIndex for consumer api
Posted by Yunze Xu <yz...@streamnative.io.INVALID>.
You need to create an issue first to start a discussion for your PIP.
Here’s the process of PIP:
1. The author(s) of the proposal will create a GitHub issue ticket choosing the
template for PIP proposals.
2. The author(s) will send a note to the dev@pulsar.apache.org <ma...@pulsar.apache.org> mailing list
to start the discussion, using subject prefix `[PIP] xxx`.
3. Based on the discussion and feedback, some changes might be applied by
authors to the text of the proposal.
4. Once some consensus is reached, there will be a vote to formally approve
the proposal.
The vote will be held on the dev@pulsar.apache.org <ma...@pulsar.apache.org> mailing list. Everyone
is welcome to vote on the proposal, though it will considered to be binding
only the vote of PMC members.
I would be required to have a lazy majority of at least 3 binding +1s votes.
The vote should stay open for at least 48 hours.
5. When the vote is closed, if the outcome is positive, the state of the
proposal is updated and the Pull Requests associated with this proposal can
start to get merged into the master branch.
Thanks,
Yunze
> 2021年9月28日 下午10:04，JiangHaiting <ji...@foxmail.com> 写道：
>
> Hi Pulsar Community,
>
>
> I'm glad to have this opportunity to propose this PIP.
>
>
> Currently we can reset the read position of a cursor by message id or timestamp.
> Since we formerly introduced index in broker metadata since 2.9.0,
> reset cursor by index is very helpful in other protocol handler (KoP or RoP).
>
>
> Also, as @BewareMyPower pointed out that
> "users might want to seek to 10000 messages before. Currently they cannot achieve this goal.".
> And this PIP will make it possible.
>
>
> I've already created a PR, see details at https://github.com/apache/pulsar/pull/12032
>
>
>
> Thanks,
> Haiting Jiang (Github:Jason918)
Re: [PIP 100] Add seekByIndex for consumer api
Posted by Yunze Xu <yz...@streamnative.io.INVALID>.
I have edited the Wiki page for PIP
https://github.com/apache/pulsar/wiki/Pulsar-Improvement-Proposal-(PIP) <https://github.com/apache/pulsar/wiki/Pulsar-Improvement-Proposal-(PIP)>
Thanks,
Yunze