Thomas Weise commented on APEXMALHAR-2284:

I will merge the change to disable the test but this needs to be fixed for 
upcoming release.

The join operator should not rely on undocumented behavior. If you want to 
ensure that you read the previous value, then you either need to do a sync get 
or you do the put when the future completes. Here is an example for different 
ways of doing this:


[~csingh] any thoughts on how this should be addressed?

Also note that the performance and scalability of this operator hasn't been 
looked at. This should be done once some of the in progress JIRAs to improve 
the performance of managed state are completed. 

> 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
>             Fix For: 3.6.0
> 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

Reply via email to