Hi all,
Would like to chime in with my interest in seeing this change! At the risk
of getting a bit off topic, I had been planning to propose a similar KIP,
but for exposing the connector name and task ID in converters and
transformers as they run into the same issue of not being able to easily
de
Hi Sarah,
Thanks for the KIP! I have two major thoughts:
1. Adding new methods like this to the Connect API comes with the risk that
connectors that invoke them become incompatible with older versions of
Connect. For example, if I updated my connector to use the newly-proposed
SourceTaskContext::
Hi all! Just wanted to bump this KIP for adding Task ID and Connector Name
to the task context. It's a small change, and I'd love some feedback on it!
Thanks!
Sarah
On Wed, Nov 24, 2021 at 10:26 AM Sarah Story <
sa...@sarahstoryengineering.com> wrote:
> I have written a KIP for adding Task ID an
I have written a KIP for adding Task ID and Connector name to the Connect
API task context.
Here is the doc: https://cwiki.apache.org/confluence/x/4pKqCw
Looking forward to hearing all of your thoughts!
