[
https://issues.apache.org/jira/browse/APEXMALHAR-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881254#comment-15881254
]
ASF GitHub Bot commented on APEXMALHAR-2422:
--------------------------------------------
GitHub user sandeshh opened a pull request:
https://github.com/apache/apex-malhar/pull/560
APEXMALHAR-2422 Flushing the data to HDFS needs a separate flag for i…
…t to work.
@otterc , @tushargosavi please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sandeshh/apex-malhar APEXMALHAR-2422
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-malhar/pull/560.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #560
----
commit 7682d368c78a4aecc84f1675ffe48fe2efa13421
Author: Sandesh Hegde <[email protected]>
Date: 2017-02-23T20:51:48Z
APEXMALHAR-2422 Flushing the data to HDFS needs a separate flag for it to
work.
----
> WindowDataManager not recovering as expected on HDFS
> ----------------------------------------------------
>
> Key: APEXMALHAR-2422
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2422
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Sandesh
> Assignee: Sandesh
>
> In WindowDataManager getLargestWindow during recovery is not reflecting the
> saved window before operator crash.
> This affects many of the operators, one example is
> KafkaExactlyOnceOutputOperator,
> https://issues.apache.org/jira/browse/APEXMALHAR-2419
> Note:
> WindowDataManager works as expected on a local machine(local filesystem), but
> not on HDFS.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
