[AVRO-1602] Remove the Dapper-style RPC trace facility

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.7
• Fix Version/s: 1.8.0
• Component/s: build

Environment

Mac OS X 10.10 Yosemite

• Hadoop Flags: Incompatible change
• Assignee: Doug Cutting
• Reporter: David Laxer
• Created: 09/Nov/14 12:21
• Updated: 14/Mar/17 21:00
• Resolved: 13/Nov/14 22:09

Description

Release Note

This change removed the Dapper-style RPC trace facility from both the Java and C# clients.

(closed issues can't have release notes added, so this is placed here instead)

Original Description

Running org.apache.avro.ipc.trace.TestFileSpanStorage
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.995 sec <<< FAILURE! - in org.apache.avro.ipc.trace.TestFileSpanStorage
testRangeQuery1(org.apache.avro.ipc.trace.TestFileSpanStorage) Time elapsed: 0.363 sec <<< FAILURE!
java.lang.AssertionError: expected:<8> but was:<4>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at org.apache.avro.ipc.trace.TestFileSpanStorage.testRangeQuery1(TestFileSpanStorage.java:159)

I see this issue:

http://apache-avro.679487.n3.nabble.com/Build-failed-in-Jenkins-AvroJava-475-td4030947.html

Is there a work-around?