[
https://issues.apache.org/jira/browse/FALCON-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122712#comment-14122712
]
Ajay Yadav commented on FALCON-338:
-----------------------------------
Sorry my bad I ran
mvn clean package -Ptest-patch, hadoop-1 -DforkMode=none
and build succeeded. I realise now that I should have used
mvn clean install -Ptest-patch, hadoop-1 -DforkMode=none.
Updating it here so that someone else doesn't do same mistake.
I discussed the review comment with [~shwethags] and she has suggested some
more discussion around it. Will create a separate JIRA ticket for that.
Providing patch without the review comment as the builds are broken currently.
> 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)
