You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/09/03 09:11:28 UTC

[GitHub] [flink] GJL commented on issue #8583: [FLINK-11820][serialization] SimpleStringSchema handle message record which value is null

GJL commented on issue #8583: [FLINK-11820][serialization] SimpleStringSchema handle message record which value is null
URL: https://github.com/apache/flink/pull/8583#issuecomment-527374604
 
 
    > Users may not care about the null values in many scenarios
   
   Users may or may not care about _nulls_. If _nulls_ have a meaning for a use case then dropping _null_ records can be fatal or lead to unexpected behavior in the worst case. According to the [ML thread](https://lists.apache.org/thread.html/2991b6b3c520380a9172588bc1f6d7e6d632c3d421458a1b44c71c01@%3Cdev.flink.apache.org%3E) Flink currently does not consistently handle _null_ records – changing that would be probably a bigger effort. All in all I think it is better to accept that `SimpleStringSchema` currently cannot be used if there are _null_ records because:
   - There are workarounds, e.g., one does not have to use `SimpleStringSchema`
   - An NPE, which will likely happen while testing the job, is better than silent data dropping in production
   
   I will close this issue. Feel free to re-open if you think otherwise.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services