+1
Looking forward to this!
Regards,
Shivji Kumar Jha
http://www.shivjijha.com/
+91 8884075512
On Mon, Apr 13, 2020 at 8:10 PM Matteo Minardi - Diennea <
minardi.mat...@hotmail.it> wrote:
> Hi everyone,
>
>
>
> Iām happy to announce the first release of Bookkeeper Visual Manager.
>
> Bookkeepe
š
Best Regards.
Jia Zhai
Beijing, China
Mobile: +86 15810491983
On Mon, Apr 13, 2020 at 2:40 AM Sijie Guo wrote:
> It seems there are no objections to this PIP. I am proceeding to create 3
> new repos to kick off the effort.
>
> https://github.com/apache/pulsar-connectors
> https://githu
:( . Some of the tests are still flaky.
If tests not get passed, user can try run failed tests individually to
verify, e.g.
"mvn test -pl pulsar-broker
-Dtest=ReplicatorTest#testUpdateGlobalTopicPartition"
Best Regards.
Jia Zhai
Beijing, China
Mobile: +86 15810491983
On Tue, Apr 14, 2020
Hi Raman,
The schema compatibility strategies were already there prior to PIP-43.
PIP-44 enhances the schema compatibility strategy support.
Both of the changes are already landed in 2.5.0 release.
Did you see any issues when you tryout this feature?
- Sijie
On Tue, Apr 14, 2020 at 8:35 AM ro
Now that PIP-43 is released in 2.5.0, I wanted to follow up on the messages
below.
What is remaining to be done in Pulsar to support having multiple different
types on one topic in Pulsar? Yi indicates below that PIP-43 sets the stage for
this, but that the schema compatibility implementation s
> I'd rather wait a bit more for that, given that apps are fetching
directly from github. Eg: change the Docs but leave the code there for
one more release cycle.
Cool, good idea, agree with you. We can remove this in next
major Apache Pulsar release. Eg: Apache Pulsar 2.6.0 or 2.7.0.
--
Thanks
2020-04-13 13:28:52 UTC - Alex Yaroslavsky: @Alex Yaroslavsky has joined the
channel
2020-04-13 22:31:52 UTC - Addison Higham: :thinking_face: have an issue with
pulsar functions worker JVM not exiting on an exception, relevant logs:
```22:20:10.304 [main] INFO
org.apache.pulsar.functions.
Thanks, Enrico, we haven't started the branch-based test yet, so it is very
difficult to ensure that all the tests can pass on the branch we are going
to release, but I think we should start the branch-based test later and
open the current Github actions ci test on each branch, which may take some
