[APEXCORE-532] New dynamically added operator does not start with correct windowId.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Assignee: Tushar Gosavi
• Reporter: Tushar Gosavi
• Created: 14/Sep/16 12:14
• Updated: 10/Dec/16 18:42
• Resolved: 22/Nov/16 19:56

Description

During dynamic DAG change, If new operator is added and connected to existing operator, it does not starts with correct windowId. The baseSeconds is set to 0 causing windowId management problems at master effectively halting purge from buffer server.

Issue Links

• links to: GitHub Pull Request #393
• links to: GitHub Pull Request #402