[FLUME-1793] Unit test TestElasticSearchLogStashEventSerializer fails with IBM JDK

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.6.0
• Component/s: Sinks+Sources, Test
• Labels: test-patch

Environment

IBM Java 6 SR 12
RHEL 6.3

• Assignee: Xiang Li
• Reporter: Aline Guedes Pinto
• Created: 18/Dec/12 15:56
• Updated: 12/Oct/15 09:38
• Resolved: 18/Jul/14 00:35

Description

TestElasticSearchLogStashEventSerializer fails with IBM JDK:
testRoundTrip(org.apache.flume.sink.elasticsearch.TestElasticSearchLogStashEventSerializer) Time elapsed: 0.201 sec <<< FAILURE!
org.junit.ComparisonFailure:expected:<...p/test","@fields":{"[timestamp":"1355151725225","src_path":"/tmp/test","host":"test@localhost","headerNameTwo":"headerValueTwo","source":"flume_tail_src","headerNameOne":"headerValueOne","type":"sometyp]e"}}^@@^@@^@@^@@^@@^@@^@@^@@...> but was:<...p/test","@fields":{"[src_path":"/tmp/test","headerNameTwo":"headerValueTwo","timestamp":"1355151725225","host":"test@localhost","type":"sometype","source":"flume_tail_src","headerNameOne":"headerValueOn]e"}}^@@^@@^@@^@@^@@^@@^@@^@@...>

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.

Issue Links

• links to: Review request 23475 on review board