[
https://issues.apache.org/jira/browse/FLINK-15940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YufeiLiu updated FLINK-15940:
-----------------------------
Description:
It's allready support copy NULL value in
[FLINK-14642|https://issues.apache.org/jira/browse/FLINK-14642]. But still get
NPE in network shuffle because of *serialize* and *deserialize* function didn't
support NULL value. It produces different behaviors when I change operator
parallelism.
*code*
{code:java}
.map().setParallelism(1)
.filter(_ != null).setParallelism(2)
{code}
*suggestion*
Add null flag in serialize, just like PojoSerializer.
was:
It's allready support copy NULL value in
[FLINK-14642|https://issues.apache.org/jira/browse/FLINK-14642]. But still get
NPE in network shuffle because of *serialize* and *deserialize* function didn't
support NULL value.
*code*
{code:java}
.map().setParallelism(1)
.filter(_ != null).setParallelism(2)
{code}
*suggestion*
Add null flag in serialize, just like PojoSerializer
> Flink TupleSerializer and CaseClassSerializer shoud support serialize and
> deserialize NULL value
> ------------------------------------------------------------------------------------------------
>
> Key: FLINK-15940
> URL: https://issues.apache.org/jira/browse/FLINK-15940
> Project: Flink
> Issue Type: Bug
> Components: API / Type Serialization System
> Affects Versions: 1.10.0
> Reporter: YufeiLiu
> Priority: Major
>
> It's allready support copy NULL value in
> [FLINK-14642|https://issues.apache.org/jira/browse/FLINK-14642]. But still
> get NPE in network shuffle because of *serialize* and *deserialize* function
> didn't support NULL value. It produces different behaviors when I change
> operator parallelism.
> *code*
> {code:java}
> .map().setParallelism(1)
> .filter(_ != null).setParallelism(2)
> {code}
> *suggestion*
> Add null flag in serialize, just like PojoSerializer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
