[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971244#comment-15971244
]
Thomas Weise commented on APEXMALHAR-2284:
------------------------------------------
What is the value this operator provides over the join accumulations that are
available with the window operator?
The previous comments here indicate design issues with the operator and how it
interacts with managed state. How would those be resolved (without duplicating
code and consistent with other implementations that use managed state)? What
are the performance characteristics of this operator?
I see a number of other tickets related to this operator. I think it is time to
get the issues addressed or the operator removed. We cannot advertise to users
that look for a solution to a common problem a defunct operator and now even
have an example for it.
> POJOInnerJoinOperator is broken
> -------------------------------
>
> Key: APEXMALHAR-2284
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2284
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Thomas Weise
> Assignee: Chaitanya
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/166322754/log.txt
> {code}
> Failed tests:
> POJOInnerJoinOperatorTest.testEmitMultipleTuplesFromStream2:337 Number of
> tuple emitted expected:<2> but was:<4>
> POJOInnerJoinOperatorTest.testInnerJoinOperator:184 Number of tuple emitted
> expected:<1> but was:<2>
> POJOInnerJoinOperatorTest.testMultipleValues:236 Number of tuple emitted
> expected:<2> but was:<3>
> POJOInnerJoinOperatorTest.testUpdateStream1Values:292 Number of tuple
> emitted expected:<1> but was:<2>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
