You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Valeria Vasylieva (JIRA)" <ji...@apache.org> on 2019/04/09 09:53:00 UTC

[jira] [Commented] (KAFKA-6755) MaskField SMT should optionally take a literal value to use instead of using null

    [ https://issues.apache.org/jira/browse/KAFKA-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813197#comment-16813197 ] 

Valeria Vasylieva commented on KAFKA-6755:
------------------------------------------

[~rhauch] discussion did not gain lot of interest from the community, should I proceed to vote, so that we finally decide if this change should be merged or discarded?

> 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)