You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Munagala V. Ramanath (JIRA)" <ji...@apache.org> on 2016/10/17 22:03:58 UTC

[jira] [Comment Edited] (APEXMALHAR-2263) Offsets in AbstractFileInputOperator should be long rather than int

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

Munagala V. Ramanath edited comment on APEXMALHAR-2263 at 10/17/16 10:03 PM:
-----------------------------------------------------------------------------

How exactly does it "break" semantic versioning ? If it is possible to break it without japicmp  complaining about it, why bother using japicmp ?



was (Author: dtram):
How exactly does it "break" semantic versioning ? If it is possible to break it without japicmp from complaining about it, why bother using japicmp ?


> Offsets in AbstractFileInputOperator should be long rather than int
> -------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2263
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2263
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>          Components: adapters other
>            Reporter: Munagala V. Ramanath
>            Assignee: Matt Zhang
>
> Offsets in AbstractFileInputOperator use the int type which means files with more that (2**31 -1) records will cause overflows and mysterious failures.
> Should be changed to use long.
>  



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