[
https://issues.apache.org/jira/browse/KAFKA-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170244#comment-16170244
]
Ewen Cheslack-Postava commented on KAFKA-4714:
----------------------------------------------
[~dhananjaydp] The record is maintained internally, but it is not exposed to
the connector. It's somewhat counter to the point of SMTs since in some cases
you may be trying to do things like remove PII, in which case you definitely
don't want to give the connector task a chance to see that data.
Regarding support for a transformation after SinkTask.put(), that doesn't
really make sense since the whole point of put() is that it passes the data to
the task to be written to the external system -- not only is the message in a
different system, it's likely been converted to some native format for that
system and is no longer in Connect's data API format.
Is there a reason you want the original value in the task? Can you describe
your use case?
> Implement remaining KIP-66 SMTs
> -------------------------------
>
> Key: KAFKA-4714
> URL: https://issues.apache.org/jira/browse/KAFKA-4714
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Fix For: 0.11.0.0
>
>
> Three didn't make it for the 0.10.2.0 release: Flatten, Cast, and
> TimestampConverter.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
