You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Matteo Merli (JIRA)" <ji...@apache.org> on 2016/03/15 01:17:33 UTC

[jira] [Assigned] (BOOKKEEPER-794) BookkeeperProtocol.Response.status is completely ignored

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Merli reassigned BOOKKEEPER-794:
---------------------------------------

    Assignee: Matteo Merli

> BookkeeperProtocol.Response.status is completely ignored
> --------------------------------------------------------
>
>                 Key: BOOKKEEPER-794
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-794
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Matteo Merli
>             Fix For: 4.4.0
>
>
> As the summary says, if you set the status to anything but ok, it will be ignored by PerChannelBookieClient. If you try to handle it, a whole load of tests fail due to different mapping for read and write requests.
> I'm running this while rebasing our auth stuff, which i'll push up when it's been validated. I means the auth stuff needs to be aware of all message types, as I can't just send a EUA error in the packet level status.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)