Hi Xiaolong, is there any progress made on this ? We would like to help on
this . Please let me know how we can proceed further
On Fri, 7 Aug 2020 at 08:34, Yuva raj wrote:
>
> https://github.com/apache/pulsar/wiki/PIP-43%3A-producer-send-message-with-different-schema
>
> Yes the above PIP works
https://github.com/apache/pulsar/wiki/PIP-43%3A-producer-send-message-with-different-schema
Yes the above PIP works for us Sijie.
On Fri, Aug 7, 2020, 2:24 AM Sijie Guo wrote:
> I think we can follow what Java client does for supporting multiple
> schemas. Does it work for you?
>
> - Sijie
>
>
Thanks Xiaolong for starting this.
I think one other aspect to look into is how to fit in nicely in the
language conventions. For example, in Go, there's already a
pre-defined way to configure JSON serialization for a struct.
>> func NewJsonSchema(jsonAvroSchemaDef string, properties map[string]s
I think we can follow what Java client does for supporting multiple
schemas. Does it work for you?
- Sijie
On Thu, Aug 6, 2020 at 1:12 PM Yuva raj wrote:
> Thanks for bringing this up xiaolong. This is very much needed feature.
> Overall looks good . Adding schema in producer options will make
Thanks for bringing this up xiaolong. This is very much needed feature.
Overall looks good . Adding schema in producer options will make one schema
bound to one producer. This works most of the time. But We produce multiple
different types of messages in single topic (Ex avro: userCreated ,
account
Hello all:
Type safety is extremely important in any application built around a message
bus like Pulsar.
Currently, Apache Pulsar supports the function of Schema Registry. And Java,
CPP and
Python clients already support schema registry related functions, In order to
further improve
the func
