You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Chinmay Kolhatkar (JIRA)" <ji...@apache.org> on 2016/11/23 12:17:58 UTC
[jira] [Resolved] (APEXMALHAR-2353) timeExpression should not be
null for time based Dedup
[ https://issues.apache.org/jira/browse/APEXMALHAR-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmay Kolhatkar resolved APEXMALHAR-2353.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 3.6.0
> timeExpression should not be null for time based Dedup
> --------------------------------------------------------
>
> Key: APEXMALHAR-2353
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2353
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Bhupesh Chawda
> Assignee: Bhupesh Chawda
> Priority: Minor
> Fix For: 3.6.0
>
>
> Time Based Dedup has timeExpression as optional. It has to be supplied by the user.
> In the current setting, if the user does not specify a timeExpression, then a different time (System time) will be passed for each tuple, irrespective of whether the tuple is a duplicate or a unique. This is a bug since even the duplicate tuples may fall in different buckets and will be concluded as unique.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)