You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2018/02/22 01:57:21 UTC

[GitHub] jvrao opened a new issue #1195: Handle optional fields gracefully in ReadExplicitLac response

jvrao opened a new issue #1195: Handle optional fields gracefully in ReadExplicitLac response
URL: https://github.com/apache/bookkeeper/issues/1195
 
 
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
    Handle optional fields gracefully in ReadExplicitLac response
      ExplicitLac and header of the last entry are optional fields in the protocol.
       Handle them as optional in the response processing
   - What did you do?
   When ledger is created and nothing is written to it, a get explicit lac
   would fail as there is no info on the bookies
   
   - What did you expect to see?
   Either lastEntry or explicitLAC should satisfy this request
   and the receiver needs to handle NULL in either of the fields. 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services