apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaitanya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2284) POJOInnerJoinOperatorTest fails in Travis CI
Date Wed, 19 Oct 2016 08:29:58 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15588040#comment-15588040

Chaitanya commented on APEXMALHAR-2284:

Join operator uses:
1) put(Slice key, Slice value, long time)
2) getAsync(Slice key)

Hence we need the following spillable structures, with above API calls but with a notion of
1. SpillableArrayListMultiMap
2. SpillableArrayList (needed by (1))
3. SpillableMap

Currently, these implementations are over ManageStateImpl. However, inner join needs it over
ManagedTimeStateImpl as time field is needed in the put() call. 

ManagedTimeMultiValueState is not duplicating the functionality in SpillableArrayListMultiMap.
It is actually a generic MultiMap implementation which has a notion of time. 
I suggest we fix the issues in ManagedTimeMultiValueState, add unit tests and fix warnings.

> 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

View raw message