GitHub user tushargosavi opened a pull request: https://github.com/apache/apex-core/pull/402
APEXCORE-532: Fix issue where new operators added to dag starts from initial checkpoint In case new operators are added dynamically, they should start from windowId of upstream operator. The issue was that new operators gets added using addLogicalOpeartor which sets recoveryWindowId to INITIAL_CHECKPOINT, which prevents getActivationCheckpoint to return correct window id of the operator during deploy. @PramodSSImmaneni please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tushargosavi/incubator-apex-core APEXCORE-532 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-core/pull/402.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 #402 ---- commit 30091217dced6d1581a8630374c942a811ab6ed2 Author: Tushar R. Gosavi <tus...@apache.org> Date: 2016-10-03T07:07:59Z APEXCORE-532: Fix issue where new operators added to dag starts from initial checkpoint ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---