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

zoucao commented on FLINK-20701:
--------------------------------

maybe you are right, it is not a good motivation, after considering carefully. 
Unit test can cover it, if only format need to be tested, and print connector 
focuses more on testing data itself than testing format. Thanks for your 
replay, [~jark].

> print connector supports outputting seriailzed record
> -----------------------------------------------------
>
>                 Key: FLINK-20701
>                 URL: https://issues.apache.org/jira/browse/FLINK-20701
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Ecosystem
>    Affects Versions: 1.13.0
>            Reporter: zoucao
>            Priority: Major
>
> Hi all, print connector is designed for debugging,and it gives us better 
> access to data. If I want to debug source connector and SQL statement, I will 
> use it to print the result. However, I don't have a good choice to observe 
> the seriailzed record, which will be sent to external connector when 
> debugging. Consequently, we 'd better make print connetcor support outputting 
> seriailzed record. We can use format=XXX to identify a seriailzed schema, 
> help user to debug and understand the process of serialization.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to