1
72%
master: 72%

Ran 01 May 2019 03:16PM UTC

Files 529

Run time 29s

Badge

Embed ▾

Committed 01 May 2019 03:16PM UTC coverage: 71.121% (-0.01%) from 71.131%

Job # 436.1

Build Type

push

jenkins

Committed by GitHub

Commit Message

Explicit error message if extent is not present on ZK (#2066)

* Explicit error message if extent is not present on ZK

Client can get no extent error in the following two scenarios.
1. When client attempted to read/open an extent that
   is not on ZK (metadata server)
2. When client attempted to read a Ledger which is on metadata
   server, but somehow missing on bookies (Data server)

It is quite confusing to get the same error, NoSuchLedgerExists
for both these cases. This checkin introduced a new error at the
BookKeeper client level, NoSuchLedgerExistsOnMetadataServer if
it is not available on ZK.

For errors related to Ledger is not available on bookie,
I left NoSuchLedgerExists as-is(instead of changing it to
NoSuchLedgerExistsOnDataServer) to minimize code changes.

This change alone provides enough distinction between these
two types of errors.

Signed-off-by: Venkateswararao Jujjuri (JV) <vjujjuri@salesforce.com>

* Checkstyle fixes

* Some more fixes

* Fixing DL test fixes

Run Details

26706 of 37550 relevant lines covered (71.12%)

0.71 hits per line

apache / bookkeeper / 436 / 1
72%
master: 72%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 436.1

apache / bookkeeper / 436 / 1 72% master: 72%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 436.1

apache / bookkeeper / 436 / 1
72%
master: 72%

README BADGES
x