[
https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571119#comment-15571119
]
Chandni Singh edited comment on APEXMALHAR-2284 at 10/13/16 7:27 AM:
---------------------------------------------------------------------
Chaitanya,
Please feel free to assign the ticket to me if my PR broke these tests. Having
a variable {code}asyncReadSource{code} didn't really make much sense to me.
Changing how reader thread fetch value from a bucket doesn't need to be exposed
and configured.
Anyways if this was done for tests, then there are better ways of doing it.
was (Author: csingh):
Chaitanya,
Please feel free to assign the ticket to me if my PR broke these tests. Having
a variable {code}asyncReadSource{code} didn't really make much sense to me.
Changing how reader thread fetch value from a bucket doesn't need to be
altered.
Anyways if this was done for tests, then there are better ways of doing it.
> POJOInnerJoinOperatorTest fails in Travis CI
> --------------------------------------------
>
> Key: APEXMALHAR-2284
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2284
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Thomas Weise
> Assignee: Chaitanya
> Priority: Blocker
>
> 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.4#6332)
