added a
line there highlighting this.
Regards
Snehashis
On Wed, Aug 21, 2024 at 9:24 PM Greg Harris
wrote:
> Hey Snehashis,
>
> Thanks for your reply!
>
> > Deviating
> > it from the spec seems unnecessary if we document it accordingly, however
> > It's
s not
found but LMK if otherwise.
Regards
Snehashis
On Mon, Aug 19, 2024 at 9:24 PM Greg Harris
wrote:
> Hi Snehashis,
>
> Sorry for the late reply.
>
> > Heterogeneous dependencies in a multi cluster deployment is highly
> discouraged
>
> Right, this remains unchan
(LMK if you want me to
take that up).
Regards
Snehashis
On Tue, Jul 2, 2024 at 12:08 AM Greg Harris
wrote:
> Hey Snehashis,
>
> Sorry for the late reply, and thanks for helping close out the discussion.
>
> > Note that if my assumptions are correct then
> > this can happe
d
inconsistent state exist in any of the connectors.
Thanks again for reviving my original KIP and working to improve it.
Looking forward to your thoughts on the points mentioned above.
Regards
Snehashis
On Wed, May 29, 2024 at 9:59 PM Chris Egerton
wrote:
> Hi Greg,
>
> First, an
Hi Greg,
That is much appreciated. No complaints on the additional scope, I will
make some time out to work on this once we have approval.
Thanks
Snehashis
On Fri, May 10, 2024 at 9:28 PM Greg Harris
wrote:
> Hey Snehashis,
>
> I'm glad to hear you're still interested in th
s and regards
Snehashis
On Fri, May 10, 2024 at 12:45 AM Greg Harris
wrote:
> Hi all,
>
> I'd like to reboot the discussion on KIP-891:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-891%3A+Running+multiple+versions+of+Connector+plugins
>
> I've ma
connector is running
underneath. This is something enforced by the connect runtime itself. All
connect CRUD operations are keyed on the connector name so there will not
be an issue.
Regards
Snehashis
On Tue, Nov 22, 2022 at 3:16 PM Sagar wrote:
> Hey Snehashsih,
>
> Thanks for the KIP. It lo
string"
> }
> },
> "required": [
> "name",
> "schema_version",
> "iam_role"
> ]
> }
>
> The connector which supports Fictional config schema 2.0 will validate the
> access key and secret key.
>
be handy as the user does not need to know the
config but beyond this it does not seem to justify its existence.
Regards
Snehashis
On Tue, Nov 22, 2022 at 10:50 AM Ashwin
wrote:
> Hi Snehasis,
>
> This is a really useful feature and thanks for initiating this discussion.
>
> I h
ng and currently
> enforces no semantics on the value it returns. Can you clarify the new
> expected semantics and explain how versions will be compared
> (alphabetical, semantics versioning, something else?)
>
> Thanks,
> Mickael
>
>
> On Mon, Nov 21, 2022 at 9:57 AM Sneha
Hi Mickael. Thanks for your input. Addressing the point you mentioned
below.
> 1) Can you explain how this would work with the GET
> /{pluginName}/config endpoint? How do you specify a version for a
> connector?
This API returns the set of configurations for a given connector. Since
between versi
+of+a+connector
Please take a look and let me know what you think.
Thank you
Snehashis Pal
Snehashis Pal created KAFKA-14410:
-
Summary: Allow connect runtime to run multiple versions of a
connector.
Key: KAFKA-14410
URL: https://issues.apache.org/jira/browse/KAFKA-14410
Project: Kafka
Hi team,
I would like to request contributor access to the project, to be able to
write KIPs and assign tickets to me.
Wiki ID: snehashisp
JIRA ID: snehashisp
Thank you
Regards
Snehashis
14 matches
Mail list logo
