[
https://issues.apache.org/jira/browse/FLINK-12900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12900:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
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.
> Refactor the class hierarchy for BinaryFormat
> ---------------------------------------------
>
> Key: FLINK-12900
> URL: https://issues.apache.org/jira/browse/FLINK-12900
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Runtime
> Reporter: Liya Fan
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The there are many classes in the class hierarchy of BinaryFormat. They share
> the same memory format:
> header + nullable bits + fixed length part + variable length part
> So many operations can be applied to a number of sub-classes. Currently, many
> such operations are implemented in each sub-class, although they implement
> identical functionality.
> This makes the code hard to understand and maintain.
> In this proposal, we refactor the class hierarchy, and move common operations
> into the base class, leaving only one implementation for each common
> operation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
