[APEXMALHAR-2299] TimeBasedDedupOperator throws exception during time bucket assignment in certain edge cases

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.0
• Fix Version/s: 3.6.0
• Assignee: Francis Fernandes
• Reporter: Francis Fernandes
• Created: 14/Oct/16 06:02
• Updated: 02/Dec/16 21:11
• Resolved: 18/Oct/16 18:50

Description

The following exception is thrown under certain edge cases:

Stopped running due to an exception. java.lang.IllegalArgumentException: new time bucket should have a value greater than the old time bucket
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:88)
	at org.apache.apex.malhar.lib.state.managed.ManagedTimeUnifiedStateImpl.handleBucketConflict(ManagedTimeUnifiedStateImpl.java:126)
	at org.apache.apex.malhar.lib.state.managed.AbstractManagedStateImpl.prepareBucket(AbstractManagedStateImpl.java:265)
	at org.apache.apex.malhar.lib.state.managed.AbstractManagedStateImpl.putInBucket(AbstractManagedStateImpl.java:276)
	at org.apache.apex.malhar.lib.state.managed.ManagedTimeUnifiedStateImpl.put(ManagedTimeUnifiedStateImpl.java:71)
	at org.apache.apex.malhar.lib.dedup.TimeBasedDedupOperator.putManagedState(TimeBasedDedupOperator.java:191)

Issue Links

• links to: GitHub Pull Request #454