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 address the edge
Hi Ashwin,
I just want to be clear that I do think there might be some value to being
able to address the edge case you've raised; I just want to understand
exactly what users might do with that information. Driving a programmatic
UI with a dropdown menu for selecting header/key/value converters
Hi Chris,
Sure, if JIRA is obsolete and does not add value, I am fine with abandoning
this change.
I will close the JIRA as well.
Thanks for helping out!
Ashwin
On Fri, Jun 24, 2022 at 4:23 AM Chris Egerton
wrote:
> Hi Ashwin,
>
> Thanks for the clarification, which is certainly useful.
Hi Ashwin,
Thanks for the clarification, which is certainly useful. However, it's not
an actual use case. What will users try to do now that would have been
difficult/impossible in the future because of this ambiguity? I ask because
the Jira ticket linked in the KIP is very old and may be
Hi Chris,
Thanks for the quick response.
> It seems pretty straightforward to get this via client-side filtering
I assume that you meant GET /collector-plugins + jq filtering on type
attribute.
One issue that I see with that approach is that we cannot filter plugins if
they implement more
Hi Ashwin,
Can you provide a use case for this new behavior? It seems pretty
straightforward to get this via client-side filtering, I'm a little
skeptical 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
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
