[ https://issues.apache.org/jira/browse/KAFKA-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785719#comment-16785719 ]
Randall Hauch commented on KAFKA-6755: -------------------------------------- [~nimfadora], the KIP looks great, and I think you could start the discussion thread. The only suggestion I would have at the moment is to make the "Compatibility, Deprecation, and Migration Plan" section a bit easier to understand by being more explicit; something like: {quote} The new configuration property in this proposal is backward compatible, so any existing connector configurations that use the MaskField SMT will continue to work as-is with no behavioral changes. To use the replacement feature, such existing connector configurations will need to be modified to add a new `replacement` property. {quote} Thanks for the contribution! > 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)