[jira] [Assigned] (FLUME-1793) Unit test TestElasticSearchLogStashEventSerializer fails with IBM JDK

["li xiang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

li xiang reassigned FLUME-1793:
-------------------------------

    Assignee: li xiang

> Unit test TestElasticSearchLogStashEventSerializer fails with IBM JDK
> ---------------------------------------------------------------------
>
>                 Key: FLUME-1793
>                 URL: https://issues.apache.org/jira/browse/FLUME-1793
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources, Test
>    Affects Versions: v1.3.0
>         Environment: IBM Java 6 SR 12
> RHEL 6.3
>            Reporter: Aline Guedes Pinto
>            Assignee: li xiang
>            Priority: Minor
>              Labels: test-patch
>             Fix For: v1.6.0
>
>         Attachments: FLUME-1793-1.patch, FLUME-1793.patch
>
>
> TestElasticSearchLogStashEventSerializer fails with IBM JDK:
> testRoundTrip(org.apache.flume.sink.elasticsearch.TestElasticSearchLogStashEventSerializer)  Time elapsed: 0.201 sec  <<< FAILURE!
> org.junit.ComparisonFailure:expected:<.....@...> but was:<.....@...>
> The values on the "@fields" element are the same as expected, but the order is different. This test case works with SUN Java though - it seems like HashMap on IBM Java and SUN Java return values in different orders, and the test case is counting on order. Order shouldn't matter when using a hashmap though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)