Comment 5 for bug 1619480

Revision history for this message
Tim Burke (1-tim-z) wrote :

This part seems curious, though:

2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:103 - Fetching 10030805 bytes starting at 9965269
2016-08-31 17:52:55 DEBUG SwiftRestClient:622 - getData:bytes=9965269-19996073
2016-08-31 17:52:55 DEBUG SwiftRestClient:1727 - GET https://storage.oraclecorp.com/v1/Storage-dfisher/qaTestData/testAvro/wine.avro
Range: bytes=9965269-19996073
X-Newest: true
X-Auth-Token: AUTH_tk2407a330ae25f8098c4e31e62f68cd8f
User-Agent: Apache Hadoop Swift Client 2.6.0-cdh5.5.0 from fd21232cef7b8c1f536965897ce20f50b83ee7b2 by jenkins source checksum 98e07176d1787150a6a9c087627562c

2016-08-31 17:52:55 DEBUG SwiftRestClient:1731 - Status code = 200
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:309 - Seek to 0; current pos =0; offset=0
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:313 - seek is no-op
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:103 - read(buffer, 0, 65536)
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:103 - read(buffer, 0, 65536)
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:309 - Seek to 0; current pos =16054; offset=-16054
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:318 - seek is backwards
2016-08-31 17:52:55 DEBUG SwiftNativeInputStream:222 - Closing HTTP input stream : seeking to 0

Why did we get a 200 instead of a 206?