Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.3.0
-
IBM Java 6 SR 12
RHEL 6.3
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.
Attachments
Attachments
Issue Links
- links to