apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Barve (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-1911) AbstractFileOutputOperator roll over boundary case
Date Mon, 07 Mar 2016 12:06:40 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182933#comment-15182933
] 

Milind Barve commented on APEXMALHAR-1911:
------------------------------------------

Deleted my previous comment as it was not for this ticket.

> AbstractFileOutputOperator roll over boundary case
> --------------------------------------------------
>
>                 Key: APEXMALHAR-1911
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-1911
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Yogi Devendra
>            Assignee: Yogi Devendra
>            Priority: Minor
>
> Case 1: 
> If maxLength is set to 100 bytes. 95 bytes are already written to file. New tuple of
10 bytes arrives on input port. This tuple will be written to the same file and output will
be rolled over to the next file after this tuple is written to the file. File size would be
105 bytes after the tuple is written. 
> This behaviour looks OK. No issues in this case. 
> Case 2:
> If maxLength is set to 100 bytes. 100 bytes are already written to file. 
> Expectation: This should immediately roll over to next file before next tuple is appended.

> Current behaviour: Roll over happens only if currentLen > maxLen . i.e. it will roll
over only after next tuple is appended.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message