[
https://issues.apache.org/jira/browse/KAFKA-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766183#comment-16766183
]
Randall Hauch commented on KAFKA-6755:
--------------------------------------
[~nimfadora], thanks for volunteering. Perhaps the best place to start for this
issue is a PR, and when that gets close we'll need to do a simple KIP before
the PR is merged. If you create a PR, please title it something like
"KAFKA-6755: Allow literal value for MaskField SMT [WIP]" and then begin the
description with "Requires KIP -- do not merge".
It is important that the SMT continues to accept configurations as used today,
so the config needs to be backward compatible.
> MaskField SMT should optionally take a literal value to use instead of using
> null
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-6755
> URL: https://issues.apache.org/jira/browse/KAFKA-6755
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 0.11.0.0
> Reporter: Randall Hauch
> Assignee: Valeria Vasylieva
> Priority: Major
> Labels: needs-kip, newbie
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> The existing {{org.apache.kafka.connect.transforms.MaskField}} SMT always
> uses the null value for the type of field. It'd be nice to *optionally* be
> able to specify a literal value for the type, where the SMT would convert the
> literal string value in the configuration to the desired type (using the new
> {{Values}} methods).
> Use cases: mask out the IP address, or SSN, or other personally identifiable
> information (PII).
> Since this changes the API, and thus will require a KIP.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
