Hello everyone,
It's been over 10 days without further discussions. Assuming everyone is
satisfied with the proposal and all questions have been addressed, we are
planning to proceed with the voting.
Thank you,
Priyanka
From: Priyanka K U
Date: Friday, 7 June 2024 at 1:53 PM
To: dev@kafka.a
and ensure that we do not open up a route for unrestricted
access to the file system.
Thanks
Priyanka
From: Greg Harris
Date: Friday, 7 June 2024 at 11:48 PM
To: dev@kafka.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] KIP-1054: Support external schemas in
JSONConverter
Hi Priyanka,
Thanks for
from a schema registry - is exactly the
same as not using schemas at all. Right?
From: dev@kafka.apache.org At: 06/07/24 14:16:13 UTC-4:00To:
dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1054: Support external schemas in JSONConverter
Hi Priyanka,
Thanks for the KIP! I think you capture
: dev@kafka.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] KIP-1054: Support external schemas in
JSONConverter
Hi Priyanka,
My suggestion is that the we can place schema file at any location, such as
file location, network location, etc. So, the new option could be just
schema.location
Best
registry - is exactly the
same as not using schemas at all. Right?
From: dev@kafka.apache.org At: 06/07/24 14:16:13 UTC-4:00To:
dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-1054: Support external schemas in JSONConverter
Hi Priyanka,
Thanks for the KIP! I think you captured the motivation well
Hi Priyanka,
Thanks for the KIP! I think you captured the motivation well: The Converter
interface on its own implies a fairly large raw message size, and the
ecosystem's strategies for deduplicating schema information are complex. I
did have some questions/concerns.
1. Have you done a comparison
Hi Priyanka,
My suggestion is that the we can place schema file at any location, such as
file location, network location, etc. So, the new option could be just
schema.location
Best,
Fan
From: Priyanka K U
Sent: Friday, June 7, 2024 16:22
To: dev@kafka.apache.o
