[
https://issues.apache.org/jira/browse/FLINK-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5284:
----------------------------------
Labels: auto-deprioritized-major auto-unassigned stale-minor (was:
auto-deprioritized-major 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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Make output of bucketing sink compatible with other processing framework like
> mapreduce
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-5284
> URL: https://issues.apache.org/jira/browse/FLINK-5284
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / FileSystem
> Reporter: Wenlong Lyu
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> Currently bucketing sink cannot move the in-progress and pending files to
> final output when the stream finished, and when recovering, the current
> output file will contain some invalid content, which can only be identified
> by the file-length meta file. These make the final output of the job
> incompatible to other processing framework like mapreduce. There are two
> things to do to solve the problem:
> 1. add direct output option to bucketing sink, which writes output to the
> final file, and delete/truncate the some file when fail over. direct output
> will be quite useful specially for finite stream job, which can enable user
> to migrate there batch job to streaming, taking advantage of features such as
> checkpointing.
> 2. add truncate by copy option to enable bucketing sink to resize output file
> by copying content valid in current file instead of creating a length meta
> file. truncate by copy will make some more extra IO operation, but can make
> the output more clean.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
