I believe that also this one must be included in 2.11.0
https://github.com/apache/pulsar/pull/18898
Since 2.11.0 system topics are enabled by default so I think we must
include this fix in 2.11.0.
For example, transactions in namespaces with encryption required, wouldn't
work at all.
Thanks,
Nico
Good viewpoint, It looks like that the AUTO_PRODUCE schema is similar to
the BYTES schema in the semantic.
So can we make the BYTES schema has the features of the AUTO_PRODUCE?
There have some reasons to do this.
Firstly, it does not cause compatibility issues. Now, the topics that have
messages se
+1 (binding)
- Penghui
On Sun, Dec 11, 2022 at 6:36 AM Enrico Olivelli wrote:
> +1 (binding)
>
> Enrico
>
> Il Ven 9 Dic 2022, 10:41 Jiaqi Shen ha scritto:
>
> > +1(non-binding)
> >
> > Thanks,
> > Jiaqi Shen
> >
> >
> > 于2022年12月5日周一 15:23写道：
> >
> > > +1(non-binding)
> > >
> > > Best,
> > >
Hi Jun,
Thanks for your PIP. Overall looks good to me.
> The Client concepts topic does not introduce the basic client concepts and
> can be enriched with content relocated from other topics. See Proposed IA for
> more details.
The link of `Proposed IA` doesn't work. Need to grant the access p
> how do you can create two Student.class in one java process? and use
the same namespace?
Could you give an example to show how `AUTO_PRODUCE` schema makes a difference?
But with AUTO_PRODUCE schema, the precondition is that we have a topic
that has messages of these two schemas.
For example, t
> It looks like that the AUTO_PRODUCE schema is similar to
the BYTES schema in the semantic.
The only differences are:
1. AUTO_PRODUCE schema can produce messages to a topic that already
has schema (because it downloaded the schema and add it to the
CommandProducer request)
2. AUTO_PRODUCE schema
GitHub user tisonkun added a comment to the discussion: [Bug] OOM on running
pulsar-perf
Cannot reproduce locally. I suspect it's about configuration issues or your
local env restrictions. Moved to the Q&A form.
GitHub link:
https://github.com/apache/pulsar/discussions/18930#discussioncommen
GitHub user Amiaozhou edited a discussion: OOM on running pulsar-perf
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and
found nothing similar.
### Version
OS：Linux version 3.10.0-1160.el7.x86_64
Pulsar： apache-pulsar-2.10.1
### Minimal
Yunze Xu 于2022年12月14日周三 20:37写道：
>
> > how do you can create two Student.class in one java process? and use
> the same namespace?
>
> Could you give an example to show how `AUTO_PRODUCE` schema makes a
> difference?
// this is Student use version0, may be data from kafka
byte[] student1 = autoCo
+1 (non-binding)
Thanks,
Bo
PengHui Li 于2022年12月14日周三 19:12写道：
>
> +1 (binding)
>
> - Penghui
>
> On Sun, Dec 11, 2022 at 6:36 AM Enrico Olivelli wrote:
>
> > +1 (binding)
> >
> > Enrico
> >
> > Il Ven 9 Dic 2022, 10:41 Jiaqi Shen ha scritto:
> >
> > > +1(non-binding)
> > >
> > > Thanks,
> > >
I still feel better to change compareTo directly.
1. Although using PulsarApiMessageId.campare() can reduce the
probability of developers using errors, it cannot be completely
avoided.
2. While a direct change would change the default behavior, I consider
it a bug, not a breaking change. We can e
Why not use the following code with a BYTES producer in your case?
```java
var schema0 = Schema.AVRO(SchemaDefinition.builder()
.withJsonDef("student with version0 json def").build();
p.newMessage(schema0).value(schema0.decode(student1)).send();
...
```
Thanks,
Yunze
On Wed, Dec 14, 2022 at
This is the second release candidate for Apache Pulsar Client Python,
version 3.0.0.
It fixes the following issues:
https://github.com/apache/pulsar-client-python/milestone/1?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Python wh
+1
Great work!
Checked:
* Signatures
* Wheel file on Mac ARM, publishing and consuming messages
* Wheel file on Alpine Linux, publishing and consuming messages
--
Matteo Merli
On Wed, Dec 14, 2022 at 7:52 AM Yunze Xu wrote:
>
> This is the second release candidate for Apache Pulsar Client
-1 (binding)
I don’t see a source release package in the dist.Apache.org directory. ASF
projects release source and everything else is a convenience.
Best,
Dave
Sent from my iPhone
> On Dec 14, 2022, at 9:08 AM, Matteo Merli wrote:
>
> +1
>
> Great work!
>
> Checked:
> * Signatures
> * Wh
+1 (binding)
- Checked the signature
- Start standalone
- Publish and consume messages
- Verified Function and State Function
- Verified Cassandra connector
- Build from the source package
Thanks,
Penghui
On Tue, Dec 13, 2022 at 7:49 PM 丛搏 wrote:
> This is the third release candidate for Apach
We also can use BYTES producer, but in BYTES schema, do not use
.newMessage(schema0), the message will not carry the schema version.
the consumer will not decode correctly.
and BYTES schema can't validate the data schema. if the data is empty
bytes array, It does not make sense to send it to the b
-1 (non-binding)
sorry, I have one question about the BatchMessageId compareTo()
method. the discussion mail :
https://lists.apache.org/thread/8n3oyk2hdsskkotnj4lnlvfnndctpqbg.
I hope it can be this issue can be discussed clearly.
I hope it can be this issue can be discussed clearly. I will retry
Hello, Pulsar community:
The cherry-pick of 2.10.3 is basically completed.
Contains 126 PRs.
link:
https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.3+
If you still have a pr that must be released in pulsar-2.10.3, please reply
to me or ping me on GitHub.
Thanks
The Apache Pulsar team is proud to announce Apache Pulsar Client C++
version 3.1.0.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor managemen
20 matches
Mail list logo
