falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-338) late data recording is enabled by default for all feeds irrespective of late arrival config
Date Thu, 04 Sep 2014 21:55:24 GMT

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

Venkatesh Seetharam commented on FALCON-338:
--------------------------------------------

[~suhas.ysr], PLS PLS run the test-patch before committing code. The review should fail if
there are violations. With your commit, the code does not even build. Can you provide a patch,
fix it and commit it please. Until then builds are broken.

> late data recording is enabled by default for all feeds irrespective of late arrival
config
> -------------------------------------------------------------------------------------------
>
>                 Key: FALCON-338
>                 URL: https://issues.apache.org/jira/browse/FALCON-338
>             Project: Falcon
>          Issue Type: Bug
>          Components: feed
>            Reporter: Venkatesh Seetharam
>            Assignee: Ajay Yadav
>         Attachments: FALCON-338-v2.patch, FALCON-338-v3.patch, falcon-338.patch
>
>
> The late data handler must only record late data for feeds configured with late arrival
cut off. It does not make sense to do it otherwise and is wasteful.
> It can be disabled in runtime.properties but then this is applicable for this install
which is undesirable.
> org.apache.falcon.entity.EntityUtil#getLateProcess



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

Mime
View raw message