[
https://issues.apache.org/jira/browse/FLINK-11102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11102:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Enable check for previous data in SpanningRecordSerializer
> ----------------------------------------------------------
>
> Key: FLINK-11102
> URL: https://issues.apache.org/jira/browse/FLINK-11102
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Affects Versions: 1.8.0
> Reporter: Nico Kruber
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> {{SpanningRecordSerializer}} only verifies that there is no left-over data
> from a previous serialization call if {{SpanningRecordSerializer#CHECKED}} is
> {{true}} but this is hard-coded as {{false}}. Now if there was previous data,
> we would silently drop this and continue with our data. The deserializer
> would probably notice and fail but identifying the root cause may not be as
> easy anymore.
> -> We should enable that check by default since the only thing it does is to
> verify {{!java.nio.Buffer#hasRemaining()}} which cannot be too expensive.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
