Hi community,
We're excited to announce Pulsar Virtual Summit Europe 2023 is happening on
May 23rd! Join us at the Summit by submitting your session here [1].
Since 2020, seven global Pulsar Summit events have featured 170+
interactive sessions by experts from Google, AWS, Splunk, Tencent, Verizo
On Tue, Feb 14, 2023 at 3:46 AM wrote:
> Hi, Asaf
>
> Welcome to join this discussion.
> > You mean that allows the *system* to use it when it's a partitioned
> topic?
> Sorry, I didn't get your point. What do you mean by *system*?
>
This sentence was a reply to:
2. Make the `-partition-` strin
Can we add another phase to this PIP - say on version x we add WARN and
override mode to non-durable, and on version x+1 we fail the client?
On Tue, Feb 14, 2023 at 9:48 AM Jiuming Tao
wrote:
> Hi Asaf,
>
> If we fail the client when users use Durable subscription to subscribe
> NonPersistentTop
>
> Additional:
> Since the disallowed topic names configuration needs more discussion about
> name pattern, type etc. I think we can wait for the demand to consider it.
>
Sounds good. We can discuss this in the future with a new proposal if there
has someone who needs it.
Yong
On Sat, 11 Feb 2
Hi all,
Our admin-client using the async-http-client [0] to request the web
service, the async-http-client implements network request based on the
netty, which has very good performance, but this project is not very active.
For security(library) reason or http feature(Follow up on future
developm
Hi Qiang
### System topic name
'__system__' I think this format is clearer.
Now the system automatically creates topics of type retry consumer letters
and dead letters.
These topics all end in uppercase letters, such as `-RETRY,` `-DLQ.`
Is it better to define the system topic name in uppercase(
'
Zixuan,
Il giorno mar 14 feb 2023 alle ore 10:36 Zixuan Liu
ha scritto:
>
> Hi all,
>
> Our admin-client using the async-http-client [0] to request the web
> service, the async-http-client implements network request based on the
> netty, which has very good performance, but this project is not ve
Hi Enrico,
> Also we can do this kind of changes only on a major release, say 3.0.0
or 3.1.0 but this is not a big problem.
Sure, we can only make this change on the major release.
> I wonder if we could use the Java HTTP client that is available on
modern JDKs in case we switch to requiring JDK
+1
Also this fix is quite important:
https://github.com/apache/pulsar-client-cpp/pull/126
Nicolò Boschi
Il giorno mar 7 feb 2023 alle ore 05:41 Baodi Shi ha
scritto:
> +1
>
> I'll do the release work on this version.
>
> Thanks,
> Baodi Shi
>
>
> 在 2023年2月1日 10:55:22 上，Zike Yang 写道：
>
> >
> Shouldn't you specify the changes you are going to make in
> `PulsarApi.proto`?
We didn't change the proto file, we use the Restful API(AdminAPI).
> Also, shouldn't you change the wording in this sentence in the PIP to
> clarify you will use AdminAPI / Pulsar RPC?
We use AdminAPI, I will tune the
+1
Release 1.8.0 is buggy and cannot be used in Production because TLS
hostname verification doesn't work
We should cut a release as soon as possible
Enrico
Il giorno mar 14 feb 2023 alle ore 11:50 Nicolò Boschi
ha scritto:
>
> +1
>
> Also this fix is quite important:
> https://github.com/apach
Hi, all
According to [0], the Nodejs client 1.8.1 will depend on C++ client
3.1.2 due to the serious OAuth2 authentication regression bug.
This release will be started after the C++ client 3.1.2 is released.
[0] https://lists.apache.org/thread/l2lmypbhw1vyyqgw99otbdth5hk74029
Thanks,
Zike Yang
Could you list all existing system topic names that are used so we can
understand the rule better? Such as the "-RETRY" and "-DLQ" topics
mentioned above.
And I saw that this proposal only forbids the creation of these
topics. What about writing messages to them? I think it's better not
to allow P
>These topics all end in uppercase letters, such as `-RETRY,` `-DLQ.`
Is it better to define the system topic name in uppercase(
'__SYSTEM__' )?
I think we don't need to mark `-DLQ` and `-RETRY` to be the keyword. because
they are the same as the normal topic for the broker side.
Best,
Mattison
> Could you list all existing system topic names that are used so we
> canunderstand the rule better?
Yes, sure. I will list it later.
> And I saw that this proposal only forbids the creation of thesetopics. What
> about writing messages to them? I think it's better notto allow Pulsar
> clients
Hi all,
We are using JDK 17 to compile all the components. For the main component,
the broker and proxy require JDK 17, and the client requires JDK 8.
In Pulsar 3.x, we should keep up with modern JDKS for all components, and
over time, I believe many users have adopted JDK 11/17, which provides
s
+1, (non-binding)
Best,
Mattison
On Dec 22, 2022, 11:24 +0800, Zixuan Liu , wrote:
> Hi all,
>
> Voting for https://github.com/apache/pulsar/issues/18798.
>
> Thanks,
> Zixuan
+1 (binding)
Regards
Jiwei Guo (Tboy)
On Wed, Feb 15, 2023 at 10:11 AM wrote:
>
> +1, (non-binding)
>
> Best,
> Mattison
> On Dec 22, 2022, 11:24 +0800, Zixuan Liu , wrote:
> > Hi all,
> >
> > Voting for https://github.com/apache/pulsar/issues/18798.
> >
> > Thanks,
> > Zixuan
+1 (binding)
- Build from source (macos x86_64 12.6)
- Run pulsar-tests with apachepulsar/pulsar:2.11.0 docker images
https://github.com/apache/pulsar-client-cpp/issues/192 I found in my env.
Thanks,
Bo
Zike Yang 于2023年2月14日周二 15:35写道：
>
> +1 (non-binding)
>
> - Build from source (macos x86_64
+1
Penghui
> On Feb 15, 2023, at 10:16, guo jiwei wrote:
>
> +1 (binding)
>
>
> Regards
> Jiwei Guo (Tboy)
>
> On Wed, Feb 15, 2023 at 10:11 AM wrote:
>>
>> +1, (non-binding)
>>
>> Best,
>> Mattison
>> On Dec 22, 2022, 11:24 +0800, Zixuan Liu , wrote:
>>> Hi all,
>>>
>>> Voting for https
I support this PIP, thank you for driving it forward Mattison.
I support using the prefix __SYSTEM__ for system topics, and I agree
that DLQ and RETRY topics do not qualify as system topics because they
are produced to and consumed by regular clients.
I think we might benefit from a generic defin
+1 binding
The tests failed with curl 7.84. upgrading to 7.87 fixed the issue.
Thanks,
Penghui
On Wed, Feb 15, 2023 at 10:36 AM 丛搏 wrote:
> +1 (binding)
>
> - Build from source (macos x86_64 12.6)
> - Run pulsar-tests with apachepulsar/pulsar:2.11.0 docker images
>
> https://github.com/apache/
I added a review to https://github.com/apache/pulsar/pull/18336.
I do not think it will be a problem to accept this PIP and to add OIDC
support. However, I think we should leave
https://github.com/apache/pulsar/issues/8152 open because this PIP
will not address the primary features requested in th
+1 (binding)
I have some comments on the PR that I'd like to discuss before it is
merged, but I consider those minor implementation details.
Thanks,
Michael
On Tue, Feb 14, 2023 at 9:02 PM PengHui Li wrote:
>
> +1
>
> Penghui
>
> > On Feb 15, 2023, at 10:16, guo jiwei wrote:
> >
> > +1 (bindin
bump
On 2023/02/13 06:56:09 Jiuming Tao wrote:
> Hi all,
>
> I would like to start a VOTE on `PIP-245: Make subscriptions of
> non-persistent topic non-durable`.
>
> Motivation:
>
> There are two types of subscriptions for a topic: Durable and Non-durable.
>
> We create a Consumer with a Du
> if we change the default
subscription mode to be non-durable for non-persistent topics, then what
will happen to users who previously had durable subscriptions on that
topic? Are we ruining something if we create non-durable subscriptions
instead?
I think it doesn't matter. Currently, the durabl
Hi, Jiuming
> bump
As for the discussion here[0], could you add a `Compatibility` section
to talk about compatibility in more detail? WDYT?
Then we could start the vote again.
[0] https://lists.apache.org/thread/2bjg39zh7z38bzbnqngbo5l4jzkjttrq
Thanks,
Zike Yang
On Wed, Feb 15, 2023 at 1:34 PM
27 matches
Mail list logo
