Hi, Baodi,
> I don't think it's a good idea to upload (napi-xx.tar.gz) to npm, these files
> are tens of MB in total, and it doesn't solve the problem that the release rc
> version needs to change the address.
If we add `Pulsar.node` (which currently included in napi-xx.tar.gz)
to npm package f
Hi all,
Jackson has a separate Java 8 support modules for adding support for proper
serialization and deserialization of new classes that were added in Java 8
(Java 8 was released in 2014).
These Jackson Java 8 support modules haven't been used in the Pulsar code base.
This is a pity. This ca
Hi, Lari:
Will it affect compatibility? If it is just an improved function, I
think it can also be added to the pulsar-common module. it adds the
dependency, so it needs PIP to discuss.
Thanks,
Bo
Lari Hotari 于2023年1月9日周一 19:06写道：
>
> Hi all,
>
> Jackson has a separate Java 8 support modules fo
+0 (binding)
- Checked signature
- Checked license for pulsar and pulsar-shell
- Build from the source code (MacOS Intel, JDK 17, Maven 3.8.6)
- Run standalone Pulsar based on Zookeeper and RocksDB metastore
- Run Pulsar-perf to produce and consume messages
- Use pulsar-shell to get topics stats
-
Any change to Jackson configuration is a potential breaking change. Yes, it
will need a PIP.
I guess we can continue to discuss the change in this thread before I create an
actual PIP which can be voted on.
-Lari
On 2023/01/09 11:53:02 丛搏 wrote:
> Hi, Lari:
>
> Will it affect compatibility? If
Hi -
I think oshi is very interesting. I really would like a discussion about how we
will use it along with how we can test for any gaps it might have. Testing will
need to consider many more types of platforms than laptops and cloud providers.
Those of us who use AWS are aware that there may b
Hello Enrico,
For your concern about temporarily increasing of retry. It can be achieved
using overriding msg property while calling reconsuming later with custom
properties..
About msg immutable as per current design if consumer call reconsumeLater
function it creates a new msg in the system add
I will draft a PIP for it.
Mattison
On Jan 9, 2023, 22:30 +0800, Dave Fisher , wrote:
> I think oshi is very interesting. I really would like a discussion about how
> we will use it along with how we can test for any gaps it might have. Testing
> will need to consider many more types of platform
Thanks for submitting this PIP, Nitin Goyal.
At the heart of this PIP is an assumption about the relationship
between producers and consumers. The PIP assumes a producer knows how
many times a consumer should attempt to consume a message before
giving up and sending it to the DLQ. Does anyone have
Congratulations, Yunze!
On 2022/12/29 12:42:36 Haiting Jiang wrote:
> Hi all,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://github.com/BewareMyPower) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
> He is very active in
Hi Hang
The upgrade does not affect it. It will automatically detect if there is
a zookeeper directory and will continue to use zookeeper.
If the new user has requirements for standalone performance, just enable
the zookeeper option.
Also, we will notice this on the release note.
Regards
Jiw
Hi all,
Currently Node.js Client is tied to specified version of C++ Client due to the
following PR:
https://github.com/apache/pulsar-client-node/pull/235
Should we bump up the version of Node.js Client even when there is no update
except for C++ Client’s upgrade(at least for critical bug fixie
Thank you all,
Close the vote with 5 bindings(PengHui, Enrico, Yunze, Jiwei, Hang), and
1non-bindings(Bo).
I will continue the release process.
Regards
Jiwei Guo (Tboy)
On Tue, Jan 10, 2023 at 10:00 AM guo jiwei wrote:
> Hi Hang
>The upgrade does not affect it. It will automatically dete
Hi, Yuto Furuta,
Currently, the latest Nodejs client 1.8.0 is already tied to the
latest C++ client 3.1.0. If there is a new C++ client version release,
I think it's also better to release a new Nodejs client version that
is tied to the latest C++ client version even though there are no new
commit
My answer is yes. Some bug fixes might be included in a newer C++
client. But I think we don't need to start a release in a hurry once a
newer C++ client is released.
Thanks,
Yunze
On Tue, Jan 10, 2023 at 3:03 PM Zike Yang wrote:
>
> Hi, Yuto Furuta,
>
> Currently, the latest Nodejs client 1.8.0
Il giorno mar 10 gen 2023 alle ore 07:18 guo jiwei
ha scritto:
>
> Thank you all,
>
> Close the vote with 5 bindings(PengHui, Enrico, Yunze, Jiwei, Hang), and
> 1non-bindings(Bo).
actually there are 2 non-binding votes:
+ Nicolò Boschi
Enrico
>
> I will continue the release process.
>
> Regards
>
16 matches
Mail list logo
