I was using the RowSerializer (package 
org.apache.flink.api.java.typeutils.runtime;) recently to serialize Rows to 
file (for reading them back in the future).
I observed a strange behavior that I would like to double check with you in 
case this is a serious problem to be addressed:
When the rowserializer is used to convert data back, there is no check for the 
consistency of the data (e.g., size of the object that was serialized, 
checksum...). This leads to situation that for random reads of bytes it can 
happen that inconsistent objects are deserialized, which of course can lead to 
inconsistent data.

For example if we serialize object of the form (Int, Long, Double, String 
String) - if we have available only 1/3 of the bytes, we can end up reading 
back objects  as (0,0,0,null, null) - this is not the only example of how the 
object can be incorrectly deserialized ...rather than having an error for this 

Hence, I wanted to double check if this is an intended behavior for some reason 
and if we should consider fixing the rowserializer to guarantee integrity of 
the objects that are deserialized.

Best regards,

Dr. Radu Tudoran
Staff Research Engineer - Big Data Expert
IT R&D Division

German Research Center
Munich Office
Riesstrasse 25, 80992 München

E-mail: radu.tudo...@huawei.com<mailto:radu.tudo...@huawei.com>
Mobile: +49 15209084330
Telephone: +49 891588344173

Hansaallee 205, 40549 Düsseldorf, Germany, 
Registered Office: Düsseldorf, Register Court Düsseldorf, HRB 56063,
Managing Director: Bo PENG, Qiuen Peng, Shengli Wang
Sitz der Gesellschaft: Düsseldorf, Amtsgericht Düsseldorf, HRB 56063,
Geschäftsführer: Bo PENG, Qiuen Peng, Shengli Wang
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

Reply via email to