You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/01/12 08:14:00 UTC

[jira] [Commented] (FLINK-25618) Data quality by apache flink

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

Martijn Visser commented on FLINK-25618:
----------------------------------------

[~tanjialiang] Thanks for opening this ticket. I think it would be best to first have a discussion on the Dev mailinglist, a discussion on Jira is suboptimal. See also https://flink.apache.org/contributing/contribute-code.html#consensus - Would you like to start a thread on this topic?

> Data quality by apache flink
> ----------------------------
>
>                 Key: FLINK-25618
>                 URL: https://issues.apache.org/jira/browse/FLINK-25618
>             Project: Flink
>          Issue Type: New Feature
>            Reporter: tanjialiang
>            Priority: Not a Priority
>
> This is discussing about how to support data quality through apache flink.
> For example, I has a sql job, a table in this job has a column named phone, and the data of the column phone must match the pattern of telephone, if not match, i can choose drop it or ignored, and we can mark it in the metrics, so that user can monitor the data of quality in source and sink.
> After this, user can kown about the data quality from the source and sink, it is useful for the downstream.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)