This release vote is cancelled since there's a new vote out for Apache Pulsar
Helm Chart 3.2.0-candidate-2:
https://lists.apache.org/thread/f0zn9882wmkwcm768v1h38ys6z5qncto
-Lari
On 2024/01/17 10:07:32 Lari Hotari wrote:
> Hello Apache Pulsar Community,
>
> This is a call for the vote to releas
Hello Apache Pulsar Community,
This is a call for the vote to release the Apache Pulsar Helm Chart version
3.2.0.
Release notes for 3.2.0-candidate-2:
https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.2.0-candidate-2
The release candidate is available at:
https://dist.apache.org
This PIP has been approved by 3 +1 (binding):
- Jiwei
- Yunze
- Penghui
Thanks,
Zixuan
Zixuan Liu 于2024年1月15日周一 17:33写道：
> Hi Pulsar Community,
>
> Voting for PIP-330: getMessagesById gets all messages
>
> PIP: https://github.com/apache/pulsar/pull/21873
> Discussion thread:
> https://lists.ap
> I see, it only affects the TTL. We can acknowledge the messages to
clean up the data. Then we have to document the `brokerInterceptors`
config clearly to say TTL might not work if
`AppendBrokerTimestampMetadataInterceptor` is not configured.
Yes, and LinLin figured out a better solution to mitig
It looks like something broke the behavior of the querystate from Pulsar
Functions.
1. The querystate exit with `Reason: key 'hello' doesn't exist`, which the
old version will not exit
```
lipenghui@lipenghuis-MacBook-Pro apache-pulsar-3.2.0 % bin/pulsar-admin
functions querystate --tenant test -
I see, it only affects the TTL. We can acknowledge the messages to
clean up the data. Then we have to document the `brokerInterceptors`
config clearly to say TTL might not work if
`AppendBrokerTimestampMetadataInterceptor` is not configured.
Thanks,
Yunze
On Thu, Jan 18, 2024 at 10:41 AM PengHui
+1 (binding)
Regards,
Penghui
On Wed, Jan 17, 2024 at 8:03 PM Yunze Xu wrote:
> +1 (binding)
>
> Thanks,
> Yunze
>
> On Wed, Jan 17, 2024 at 6:55 PM guo jiwei wrote:
> >
> > +1 (binding)
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Wed, Jan 17, 2024 at 5:39 PM 太上玄元道君 wrote:
> >
> >
> I don't think we should provide such an option for users. Compared
with the serious security issue, the extra overhead (13 bytes) per
entry (not per message) should never be a concern.
It actually changed the stored data format. As far as I know, there are
some users
who read data from the offlo
> We should also improve the TTL:
> When client publish time > Ledger create time + Ledger rollover time,
> and `brokerPublishTime` is not set,
> we can make Ledger TTL time = Ledger create time + Ledger rollover time.
> This change can make sure entry expires when client clock is not right.
Thi
>From my perspective, it's a serious security issue. The client side
could easily make Pulsar's message expiry mechanism not work. Even if
it's not a malicious change made by users, it would be hard to figure
out what makes the message not expired.
> Users can still have a way to disable it if the
+1 (binding)
Thanks,
Yunze
On Wed, Jan 17, 2024 at 6:55 PM guo jiwei wrote:
>
> +1 (binding)
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Wed, Jan 17, 2024 at 5:39 PM 太上玄元道君 wrote:
>
> > +1 nonbinding
> >
> >
> > > 2024年1月17日 17:35，Asaf Mesika 写道：
> > >
> > > +1 (non-binding)
> > >
> > > On Tue,
+1 (binding)
Regards
Jiwei Guo (Tboy)
On Wed, Jan 17, 2024 at 5:39 PM 太上玄元道君 wrote:
> +1 nonbinding
>
>
> > 2024年1月17日 17:35，Asaf Mesika 写道：
> >
> > +1 (non-binding)
> >
> > On Tue, Jan 16, 2024 at 4:43 AM Dezhi Liu wrote:
> >
> >> +1 (non-binding)
> >>
> >> Thanks,
> >> Dezhi Liu
> >>
> >>
Only enabled `AppendBrokerTimestampMetadataInterceptor` is not enough.
We should also improve the TTL:
When client publish time > Ledger create time + Ledger rollover time,
and `brokerPublishTime` is not set,
we can make Ledger TTL time = Ledger create time + Ledger rollover time.
This change c
Hello Apache Pulsar Community,
This is a call for the vote to release the Apache Pulsar Helm Chart version
3.2.0.
Release notes for 3.2.0-candidate-1:
https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.2.0-candidate-1
The release candidate is available at:
https://dist.apache.org
+1 nonbinding
> 2024年1月17日 17:35，Asaf Mesika 写道：
>
> +1 (non-binding)
>
> On Tue, Jan 16, 2024 at 4:43 AM Dezhi Liu wrote:
>
>> +1 (non-binding)
>>
>> Thanks,
>> Dezhi Liu
>>
>> On 2024/01/15 09:33:48 Zixuan Liu wrote:
>>> Hi Pulsar Community,
>>>
>>> Voting for PIP-330: getMessagesById g
+1 (non-binding)
On Tue, Jan 16, 2024 at 4:43 AM Dezhi Liu wrote:
> +1 (non-binding)
>
> Thanks,
> Dezhi Liu
>
> On 2024/01/15 09:33:48 Zixuan Liu wrote:
> > Hi Pulsar Community,
> >
> > Voting for PIP-330: getMessagesById gets all messages
> >
> > PIP: https://github.com/apache/pulsar/pull/2187
16 matches
Mail list logo
