[
https://issues.apache.org/jira/browse/FLINK-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10003:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
