flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10005) StreamingFileSink ignores checkpoint/processing time rolling policies
Date Wed, 01 Aug 2018 06:52:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564842#comment-16564842

ASF GitHub Bot commented on FLINK-10005:

kl0u commented on issue #6466: [FLINK-10005][DataStream API] StreamingFileSink: sets initialPartCounter=maxUsed
in new Buckets
URL: https://github.com/apache/flink/pull/6466#issuecomment-409468865
   Because this will close the previous AND open a new part file, meaning all buckets, active
and inactive, will always be in state. Which we do not want. Also, it means that a bucket
that has specified a `rollingInterval` will have a lot of empty part files, as they will open,
receive no elements, close due to timeout, and open the next one.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> StreamingFileSink ignores checkpoint/processing time rolling policies
> ---------------------------------------------------------------------
>                 Key: FLINK-10005
>                 URL: https://issues.apache.org/jira/browse/FLINK-10005
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming Connectors
>    Affects Versions: 1.6.0
>            Reporter: Chesnay Schepler
>            Assignee: Kostas Kloudas
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.6.0
> The {{StreamingFileSink}} supports different policies to determine whether a new part
file should be created; on each checkpoint, once a certain size is reached or on processing
> This feature only works correctly for size thresholds, other policies are ignored.

This message was sent by Atlassian JIRA

View raw message