I think the primary point is that unless there is a strict need, we
shouldn't introduce breaking changes to the implementation. Why did we
choose to forbid users from uploading a Bytes schema? Did we consider
making a call to upload a Bytes schema a no-op?
Thanks,
Michael
On Fri, Apr 14, 2023 at
1. I don't know much about flink, but what I see here is that you need to
save a `ResolvedCatalogTable`, which I see has `CatalogTable`, so it is
used to record the metadata information of the table.
**In
org.apache.flink.connector.pulsar.table.catalog.impl.PulsarCatalogSupport#createTable**
```jav
Il giorno ven 14 apr 2023 alle ore 16:48 Christophe Bornet
ha scritto:
>
> The change was not reverted for 3.0.0-RC so in the current state the
> Flink Pulsar catalog won't work with Pulsar 3.0.
> To give more details, Flink Pulsar stores Flink Table metadata in the
> metadata of BYTES schema topi
The change was not reverted for 3.0.0-RC so in the current state the
Flink Pulsar catalog won't work with Pulsar 3.0.
To give more details, Flink Pulsar stores Flink Table metadata in the
metadata of BYTES schema topics (those topics don't have messages,
only the schema metadata of these topics is
Hi guys,
Thanks for Micheal's great job, and he already pushed one PR [1]
to fix this bug on the BookKeeper side. This comment [2] shows how
this bug happens.
I will cut BookKeeper 4.16.1 release soon.
Thanks,
Hang
[1] https://github.com/apache/bookkeeper/pull/3919
[2] https://github.com/ap
Hi everyone,
This is the first release candidate for Apache Pulsar Node.js client,
version 1.8.2.
It fixes the following issues:
https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed
Please download the source files and review this release candidate:
-
