Hi Devs,
I still want to sell this idea :) I think it would be really beneficial for
the MM2 to have a proper REST API, to monitor the state of the replication
flows.
Please share your opinion on this.
Thank you!
On Tue, Mar 25, 2025 at 1:46 PM Kondrát Bertalan wrote:
> Hi Team,
&g
Hi Team,
I appreciate any feedback on this KIP, KIP-1144: Exposing a new public REST
API for MirrorMaker2
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-1144%3A+Exposing+a+new+public+REST+API+for+MirrorMaker+2>
.
Thank you!
On Fri, Mar 14, 2025 at 4:07 PM Kondrát Bertalan wrote:
Hi All,
I would like to start a discussion thread about the KIP-1144: Exposing a
new public REST API for MirrorMaker2
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-1144%3A+Exposing+a+new+public+REST+API+for+MirrorMaker+2>
This KIP introduces a new REST API tailored for Mirror
Hi All,
I have to make some correction to the description: so the KIP-710
introduced the REST API to solve the problem with the inter worker
communication. Previously, there were no REST APIs in MM2. Exposing the
full Connect API is a rejected alternative.
On Fri, Mar 14, 2025 at 12:38 PM
Bertalan Kondrat created KAFKA-18985:
Summary: Exposing a new public REST API for MirrorMaker2
Key: KAFKA-18985
URL: https://issues.apache.org/jira/browse/KAFKA-18985
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Egerton resolved KAFKA-10816.
---
Fix Version/s: 3.9.0
Resolution: Done
> Connect REST API should have a resource t
Mickael Maison created KAFKA-16881:
--
Summary: InitialState type leaks into the Connect REST API OpenAPI
spec
Key: KAFKA-16881
URL: https://issues.apache.org/jira/browse/KAFKA-16881
Project: Kafka
> >
> > > > > I'd like to put the subj KIP[1] to a vote. Thank you.
> > > > >
> > > > > Best regards,
> > > > > Ivan
> > > > >
> > > > > [1]
> > > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
> > > > >
> > > >
> > >
>
; >
> > > > Best regards,
> > > > Ivan
> > > >
> > > > [1]
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
> > > >
> > >
> >
gt; > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
> > >
> >
>
Best regards,
> > Ivan
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
> >
>
+for+connector+config+in+Connect+REST+API
>
Hello!
I'd like to put the subj KIP[1] to a vote. Thank you.
Best regards,
Ivan
[1]
https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
t; > > >
> > > > On Tue, Mar 26, 2024, at 14:19, Ivan Yurchenko wrote:
> > > > > Hi all,
> > > > >
> > > > > This KIP is a bit old now :) but I think its context hasn't changed
> > > much since then and the KIP is still vali
; > > Hi all,
> > > >
> > > > This KIP is a bit old now :) but I think its context hasn't changed
> > much since then and the KIP is still valid. I would like to finally bring
> > it to some conclusion.
> > > >
> > > > Best,
> &g
> it to some conclusion.
> > >
> > > Best,
> > > Ivan
> > >
> > > On 2021/07/12 14:49:47 Chris Egerton wrote:
> > > > Hi all,
> > > >
> > > > Know it's been a while for this KIP but in my personal experience
> th
to finally bring it to
> > some conclusion.
> >
> > Best,
> > Ivan
> >
> > On 2021/07/12 14:49:47 Chris Egerton wrote:
> > > Hi all,
> > >
> > > Know it's been a while for this KIP but in my personal experience th
is Egerton wrote:
> > Hi all,
> >
> > Know it's been a while for this KIP but in my personal experience the value
> > of a PATCH method in the REST API has actually increased over time and I'd
> > love to have this option for quick, stop-the-bleeding remediat
this KIP but in my personal experience the value
> of a PATCH method in the REST API has actually increased over time and I'd
> love to have this option for quick, stop-the-bleeding remediation efforts.
>
> One thought that comes to mind is that sometimes it may be useful to
&
rnal endpoints that workers
> use to communicate with one another are enabled.
>
> If you want the other endpoints for getting the status, reconfiguring
> connectors, etc, I would recommend switching to the connect distributed
> mode and creating the MM2 connectors via the REST API.
>
&
to the connect distributed
mode and creating the MM2 connectors via the REST API.
Hope this helps!
Greg
On Sun, Feb 18, 2024 at 2:00 AM aaron ai wrote:
> Kafka Development Team:
>
> I have enabled the internal REST API for the dedicated mode by setting
> *dedicated.mode.enable.in
Kafka Development Team:
I have enabled the internal REST API for the dedicated mode by setting
*dedicated.mode.enable.internal.rest* to true in my MM2 configuration
since KIP-710:
Full support for distributed mode in dedicated MirrorMaker 2.0 clusters
<https://cwiki.apache.org/confluence/disp
s via query parameters along with a couple of related small improvements.
>
> KIP -
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-882%3A+Kafka+Connect+REST+API+timeout+improvements
>
> Discussion thread -
> https://lists.apache.org/thread/cygy115qmwpc3nj5omnj0crws2dw8nor
>
> Thanks,
> Yash
>
rgs constructor are visible in the REST
> API
> -
>
> Key: KAFKA-14863
> URL: https://issues.apache.org/jira/browse/KAFKA-14863
> Project: Kafka
>
Greg Harris created KAFKA-14863:
---
Summary: Plugins which do not have a valid no-args constructor are
visible in the REST API
Key: KAFKA-14863
URL: https://issues.apache.org/jira/browse/KAFKA-14863
ea but
> I'm
> > not sure whether this KIP should take into consideration a hypothetical
> > future proposal? If there were already such a concrete proposal, I would
> > definitely agree that this KIP should take that into consideration - but
> > that isn't
ion API in the future?
>
> Thanks,
> Yash
>
> On Sat, Mar 4, 2023 at 1:13 AM Greg Harris
> wrote:
>
> > Yash,
> >
> > 1.
> > Currently the request parameters in the REST API are individual and
> pertain
> > to just one endpoint.
> > They a
sh,
>
> 1.
> Currently the request parameters in the REST API are individual and pertain
> to just one endpoint.
> They also change the content of the query result, or change the action
> taken on the cluster.
> I think that a request timeout is a property of the HTTP reques
Chris Egerton created KAFKA-14784:
-
Summary: Implement connector offset reset REST API
Key: KAFKA-14784
URL: https://issues.apache.org/jira/browse/KAFKA-14784
Project: Kafka
Issue Type: Sub
Chris Egerton created KAFKA-14785:
-
Summary: Implement connector offset read REST API
Key: KAFKA-14785
URL: https://issues.apache.org/jira/browse/KAFKA-14785
Project: Kafka
Issue Type: Sub
Yash,
1.
Currently the request parameters in the REST API are individual and pertain
to just one endpoint.
They also change the content of the query result, or change the action
taken on the cluster.
I think that a request timeout is a property of the HTTP request more than
it is a property of
IP-882
> > which adds support for configuring request timeouts on Kafka Connect REST
> > APIs via query parameters along with a couple of related small
> > improvements.
> >
> > KIP -
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-882%3A+Kafka+Connect+REST+API+timeout+improvements
> >
> > Discussion thread -
> > https://lists.apache.org/thread/cygy115qmwpc3nj5omnj0crws2dw8nor
> >
> > Thanks,
> > Yash
> >
>
u consider adding asynchronous validation as a user-facing
> feature? I think that relying on the synchronous validation results in a
> single HTTP request is a bit of an anti-pattern, and one that we've
> inherited from the original REST design. It seems useful when using the
> REST A
. Did you consider adding asynchronous validation as a user-facing
feature? I think that relying on the synchronous validation results in a
single HTTP request is a bit of an anti-pattern, and one that we've
inherited from the original REST design. It seems useful when using the
REST API by hand
for a vote on the (hopefully) straightforward KIP-882
> which adds support for configuring request timeouts on Kafka Connect REST
> APIs via query parameters along with a couple of related small
> improvements.
>
> KIP -
>
> https://cwiki.apache.org/confluence/display/KAFKA/K
2
> which adds support for configuring request timeouts on Kafka Connect REST
> APIs via query parameters along with a couple of related small improvements.
>
> KIP -
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-882%3A+Kafka+Connect+REST+API+timeout+improvements
&g
Hi all,
Thanks for all the feedback and discussion. I've renamed the KIP title to
"Kafka Connect REST API timeout improvements" since we're introducing a
couple of improvements (cancelling create / update connector requests when
config validations timeout and avoiding double c
82%3A+Kafka+Connect+REST+API+timeout+improvements
Discussion thread -
https://lists.apache.org/thread/cygy115qmwpc3nj5omnj0crws2dw8nor
Thanks,
Yash
lingsbigm created KAFKA-14736:
-
Summary: Kafka Connect REST API: POST/PUT/DELETE requests are not
working
Key: KAFKA-14736
URL: https://issues.apache.org/jira/browse/KAFKA-14736
Project: Kafka
Chris Egerton created KAFKA-14645:
-
Summary: Plugin classloader not used when retrieving connector
plugin config defs via REST API
Key: KAFKA-14645
URL: https://issues.apache.org/jira/browse/KAFKA-14645
ue as KAFKA-14545
> Crashed MirrorCheckpointConnector appears as running in REST API
>
>
> Key: KAFKA-14072
> URL: https://issues.apache.org/jira/browse/KAFKA-14072
> Project:
Yash Mayya created KAFKA-14368:
--
Summary: Add an offset write REST API to Kafka Connect
Key: KAFKA-14368
URL: https://issues.apache.org/jira/browse/KAFKA-14368
Project: Kafka
Issue Type: New
n the scope. The current behavior where the API
> >> > > response indicates a time out but the connector is created/updated
> >> > > eventually anyway can be pretty confusing and is generally not a
> good
> >> > user
> >> > > experience IM
gt;> > > experience IMO.
>> > >
>> > > 2. Wow, thanks for pointing this out - it's a really good catch and
>> > > something I hadn't noticed was happening with the current
>> implementation.
>> > > While I do like the idea
; > While I do like the idea of having a query parameter that determines
> > > whether validations can be skipped, I'm wondering if it might not be
> > easier
> > > and cleaner to just do the leader check earlier and avoid doing the
> > > unnecessary config vali
necessary config validation on the first worker? Since each config
> > validation happens on its own thread, I'm not so sure about the concern
> of
> > overloading the leader even on larger clusters, especially since
> > validations aren't typically long running ope
er? Since each config
> validation happens on its own thread, I'm not so sure about the concern of
> overloading the leader even on larger clusters, especially since
> validations aren't typically long running operations. Furthermore, even
> with the current implementation, th
oncern of
overloading the leader even on larger clusters, especially since
validations aren't typically long running operations. Furthermore, even
with the current implementation, the leader will always be doing a config
validation for connector create / update REST API requests on any worker
ader.
3. A worker property is pretty coarse-grained, and difficult to change. We
might allow per-request toggling of the timeout by adding a URL query
parameter like '?timeout=90s' to the REST API to allow tweaking of the
timeout on a more granular basis, and without having to perform a w
Hi all,
I'd like to start a discussion thread on this small KIP -
https://cwiki.apache.org/confluence/display/KAFKA/KIP-882%3A+Make+Kafka+Connect+REST+API+request+timeouts+configurable
It proposes the addition of a new Kafka Connect worker configuration to
allow configuring REST API re
ct
>Affects Versions: 3.2.0
>Reporter: Alexandre Garnier
>Assignee: Alexandre Garnier
>Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> Prior to 2.2.1, when an REST API request was pe
Alexandre Garnier created KAFKA-14099:
-
Summary: No REST API request logs in Kafka connect
Key: KAFKA-14099
URL: https://issues.apache.org/jira/browse/KAFKA-14099
Project: Kafka
Issue
Mickael Maison created KAFKA-14072:
--
Summary: Crashed MirrorCheckpointConnector appears as running in
REST API
Key: KAFKA-14072
URL: https://issues.apache.org/jira/browse/KAFKA-14072
Project: Kafka
No worries Chris - I understand what you are getting at.
I will pursue updating the current REST API.
Cheers,
Ashwin
On Fri, Jun 24, 2022 at 8:57 AM Chris Egerton
wrote:
> Hi Ashwin,
>
> I just want to be clear that I do think there might be some value to being
> able to addr
rters could be
one such use case, for example.
If we do decide to tweak the REST API to expose multiple types for classes
that implement multiple plugins, we'll still need a KIP for that, and I'd
be happy to review if you wanted to pursue that. I'm also not dead-set
against the filter
y to address the edge case of a class
> implementing multiple plugin interfaces: we can just expose each type in
> the REST API, instead of picking one at random.
>
> Cheers,
>
> Chris
>
> On Thu, Jun 23, 2022 at 12:55 AM Ashwin
> wrote:
>
> > Hi Chris,
&g
ay be obsolete, and
there seems to be a much simpler way to address the edge case of a class
implementing multiple plugin interfaces: we can just expose each type in
the REST API, instead of picking one at random.
Cheers,
Chris
On Thu, Jun 23, 2022 at 12:55 AM Ashwin
wrote:
> Hi Chris,
>
>
eptical that we need to implement it server-side.
>
> Cheers,
>
> Chris
>
> On Wed, Jun 22, 2022 at 4:25 AM Ashwin
> wrote:
>
> > Hello Folks,
> >
> > I have picked up a newbie task and request you provide your valuable
> > feedback.
> >
> > KIP:
have picked up a newbie task and request you provide your valuable
> feedback.
>
> KIP:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-850%3A+REST+API+for+filtering+Connector+plugins+by+type
> Initial PR: https://github.com/apache/kafka/pull/12330
>
> Though https
Hello Folks,
I have picked up a newbie task and request you provide your valuable
feedback.
KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-850%3A+REST+API+for+filtering+Connector+plugins+by+type
Initial PR: https://github.com/apache/kafka/pull/12330
Though https://issues.apache.org
[
https://issues.apache.org/jira/browse/KAFKA-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-13780.
Fix Version/s: 3.3.0
Resolution: Fixed
> Generate docs for Connect REST
[
https://issues.apache.org/jira/browse/KAFKA-13442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass resolved KAFKA-13442.
-
Resolution: Duplicate
> REST API endpoint for fetching a connector'
Mickael Maison created KAFKA-13780:
--
Summary: Generate docs for Connect REST API
Key: KAFKA-13780
URL: https://issues.apache.org/jira/browse/KAFKA-13780
Project: Kafka
Issue Type
Viktor Somogyi-Vass created KAFKA-13442:
---
Summary: REST API endpoint for fetching a connector's config
definition
Key: KAFKA-13442
URL: https://issues.apache.org/jira/browse/KAFKA-13442
Pr
Hi all,
Know it's been a while for this KIP but in my personal experience the value
of a PATCH method in the REST API has actually increased over time and I'd
love to have this option for quick, stop-the-bleeding remediation efforts.
One thought that comes to mind is that sometimes
raphael auv created KAFKA-12871:
---
Summary: Kafka-connect : rest api connect config, fields are not
ordered
Key: KAFKA-12871
URL: https://issues.apache.org/jira/browse/KAFKA-12871
Project: Kafka
in Connect REST API
> ---
>
> Key: KAFKA-10833
> URL: https://issues.apache.org/jira/browse/KAFKA-10833
> Project: Kafka
> Issue Type: Improvement
>
Mickael Maison created KAFKA-10833:
--
Summary: KIP-661: Expose task configurations in Connect REST API
Key: KAFKA-10833
URL: https://issues.apache.org/jira/browse/KAFKA-10833
Project: Kafka
; > >
> > > > I definitely needed this capability a few times before. Thank you.
> > > >
> > > > +1 (binding)
> > > >
> > > > On Thu, Sep 24, 2020 at 7:54 AM Mickael Maison <
> > mickael.mai...@gmail.com>
&g
Randall Hauch created KAFKA-10816:
-
Summary: Connect REST API should have a resource that can be used
as a readiness probe
Key: KAFKA-10816
URL: https://issues.apache.org/jira/browse/KAFKA-10816
Thank you.
> > >
> > > +1 (binding)
> > >
> > > On Thu, Sep 24, 2020 at 7:54 AM Mickael Maison <
> mickael.mai...@gmail.com>
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > >
P-661:
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
> > >
> > > Thanks
> >
> >
> >
> > --
> > Gwen Shapira
> > Engineering Manager | Confluent
> > 650.450.2760 | @gwenshap
> > Follow us: Twitter | blog
> >
> >
; > I'd like to start a vote on KIP-661:
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
> >
> > Thanks
>
>
>
> --
> Gwen Shapira
> Engineering Manager | Confluent
> 650.450.2760 | @gwenshap
> Follow us: Twitter | blog
>
>
I definitely needed this capability a few times before. Thank you.
+1 (binding)
On Thu, Sep 24, 2020 at 7:54 AM Mickael Maison wrote:
>
> Hi,
>
> I'd like to start a vote on KIP-661:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations
Looks a nice proposal. +1
On 2020/09/24 14:53:47, Mickael Maison wrote:
> Hi,
>
> I'd like to start a vote on KIP-661:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
>
> Thanks
>
M Mickael Maison
>> wrote:
>>
>> Hi,
>>
>> I'd like to start a vote on KIP-661:
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
>>
>> Thanks
P-661%3A+Expose+task+configurations+in+Connect+REST+API
>
> Thanks
Hi,
I'd like to start a vote on KIP-661:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
Thanks
;
> On Thu, Aug 20, 2020 at 5:47 PM Mickael Maison
> wrote:
> >
> > Hi,
> >
> > I've created KIP-661 expose the configuration of individual tasks in
> > the Connect API
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+config
sks in
> the Connect API
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
>
> Please take a look and let me know if you have any feedback.
>
> Thanks
Hi,
I've created KIP-661 expose the configuration of individual tasks in
the Connect API
https://cwiki.apache.org/confluence/display/KAFKA/KIP-661%3A+Expose+task+configurations+in+Connect+REST+API
Please take a look and let me know if you have any feedback.
Thanks
[
https://issues.apache.org/jira/browse/KAFKA-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis resolved KAFKA-9810.
---
Resolution: Fixed
> Document Connect Root REST API
Konstantine Karantasis created KAFKA-9810:
-
Summary: Document Connect Root REST API on /
Key: KAFKA-9810
URL: https://issues.apache.org/jira/browse/KAFKA-9810
Project: Kafka
Issue
Hi Team,
I need to configure a REST API as the source but I am not getting any
document for the same. Can you please share some link or documents which
can help me. Thanks in advance.
--
Thanks & Regards,
Kundan Singh
I agree Matthias. I also see the metadata stored in the value of the topic
status record being extended in the near future to include additional
useful information.
I'm happy to announce that we met our first deadline and that this KIP has
been approved with:
3 binding +1 votes from Randall Hauch
Thanks for the KIP.
I am not sure how useful the timestamp and taskId information will be in
practice, but I don't have any concern with regard to
overhead/performance. Hence, as you think it might be useful, I trust
your judgement.
For the timestamp though, I would like to emphasize that I perso
Thanks for the KIP Konstantine. This will be very useful for Connect.
+1(binding)
-Bill
On Tue, Jan 21, 2020 at 2:12 PM Almog Gavra wrote:
> Another thanks from me! +1 (non-binding)
>
> On Tue, Jan 21, 2020 at 11:04 AM Randall Hauch wrote:
>
> > Thanks again for the KIP and this improvement
Another thanks from me! +1 (non-binding)
On Tue, Jan 21, 2020 at 11:04 AM Randall Hauch wrote:
> Thanks again for the KIP and this improvement for Connect.
>
> +1 (binding)
>
> Randall
>
> On Tue, Jan 21, 2020 at 10:45 AM Tom Bentley wrote:
>
> > +1 (non-binding). Thanks for the KIP Konstantine
Thanks again for the KIP and this improvement for Connect.
+1 (binding)
Randall
On Tue, Jan 21, 2020 at 10:45 AM Tom Bentley wrote:
> +1 (non-binding). Thanks for the KIP Konstantine.
>
> On Sat, Jan 18, 2020 at 2:18 AM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
>
> > Hi all,
+1 (non-binding). Thanks for the KIP Konstantine.
On Sat, Jan 18, 2020 at 2:18 AM Konstantine Karantasis <
konstant...@confluent.io> wrote:
> Hi all,
>
> I'd like to open the vote on KIP-558 that had a constructive flurry of
> discussions in the past few days, in order to give this KIP the opport
Hi all,
I'd like to open the vote on KIP-558 that had a constructive flurry of
discussions in the past few days, in order to give this KIP the opportunity
to be voted on by the current KIP deadline (Wed, Jan 22, 2020), if - of
course - there's agreement upon its final form.
KIP link here:
https:/
Kedar Shenoy created KAFKA-9442:
---
Summary: Kafka connect REST API times out when trying to create a
connector
Key: KAFKA-9442
URL: https://issues.apache.org/jira/browse/KAFKA-9442
Project: Kafka
CVE-2019-12399: Apache Kafka Connect REST API may expose plaintext secrets
in tasks endpoint
Severity: Medium
Vendor: The Apache Software Foundation
Versions Affected:
Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.3.0
Description:
When Connect workers in Apache Kafka 2.0.0, 2.0.1
pic whitelist through
> REST API
> ---
>
> Key: KAFKA-9345
> URL: https://issues.apache.org/jira/browse/KAFKA-9345
> Project: Kafka
> Issue Type: B
yzhou created KAFKA-9345:
Summary: Deploy Mirror Maker 2.0 and dynamically modify the topic
whitelist through REST API
Key: KAFKA-9345
URL: https://issues.apache.org/jira/browse/KAFKA-9345
Project: Kafka
://cwiki.apache.org/confluence/display/KAFKA/KIP-297%3A+Externalizing+Secrets+for+Connect+Configurations)
were introduced.
> Connect REST API exposes plaintext secrets in tasks endpoint if config value
> contains additional char
Oleksandr Diachenko created KAFKA-8774:
--
Summary: Connect REST API exposes plaintext secrets in tasks
endpoint
Key: KAFKA-8774
URL: https://issues.apache.org/jira/browse/KAFKA-8774
Project
-band
> data source, e.g. Kafka or Zookeeper, and then have your Connector
> subscribe to changes. I've done something like this to enable dynamic
> reconfiguration of Connectors from command-line tools and dashboards
> without involving the Connect REST API at all. Moreover, I&#x
t change a lot, it's possible to use an out-of-band
data source, e.g. Kafka or Zookeeper, and then have your Connector
subscribe to changes. I've done something like this to enable dynamic
reconfiguration of Connectors from command-line tools and dashboards
without involving the Connect R
t; connector config in Connect REST API.
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
>
> There is also a draft PR: https://github.com/apache/kafka/pull/6934.
>
> Thank you.
>
> Ivan
>
1 - 100 of 307 matches
Mail list logo
