[
https://issues.apache.org/jira/browse/FLINK-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328595#comment-17328595
]
Flink Jira Bot commented on FLINK-10003:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Encoder interface inefficient when wanting to use more sophisticated
> outputstreams
> ----------------------------------------------------------------------------------
>
> Key: FLINK-10003
> URL: https://issues.apache.org/jira/browse/FLINK-10003
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common
> Affects Versions: 1.6.0
> Reporter: Chesnay Schepler
> Priority: Major
> Labels: stale-major
>
> The {{StreamingFileSink}} uses the {{Encoder}} interface to serialize data.
> {code}
> public interface Encoder<IN> extends Serializable {
> void encode(IN element, OutputStream stream) throws IOException;
> }
> {code}
> The implementation (with the exception for strings) must be provided by the
> user.
> To use any {{OutputStream}} implementation that is a little more convenient
> than the base {{OutputStream}} (like {{DataOutputStream}}) requires creating
> a new stream for every single record. If an implementation is used that
> potentially buffers data users additionally have to call {{flush()}}.
> Instead we could allow specifying an optional factory for the streams, that
> would be called once for each part file, and modify the {{Encoder}} interface
> to have a generic type for the output stream.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
