hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9421) Convert SASL to use ProtoBuf and add lengths for non-blocking processing
Date Fri, 17 May 2013 13:43:17 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660718#comment-13660718

Daryn Sharp commented on HADOOP-9421:

I'm not doing a big bang change of all proposed improvements.  I'm just trying to protobuf
the auth negotiation and keep track of the SASL state to remove the hack for the PLAIN mech.
 My goal is a minimal change that I can build upon w/o introducing future incompatibility.
 I'm deferring the client use of the advertised auth methods although the server will send
it.  Clients will dictate the mech/proto on connect - which will be how client reconnects
will work per Luke and I's discussion.

I'm curious how RPC v9 testing is blocked by the SASL changes?  Isn't there value is stressing
what's there, and then testing the SASL changes when it's done - which is likely to primarily
be done by Yahoo (me)?  The demo patch appears to propagate the current limited design which
will be very difficult to support in combination with the new design.  Ie. the switch to simple.
 I'm also not sure why the SASL protobuf should contain error messages instead of leverage
the existing error/fatal RPC response.
> Convert SASL to use ProtoBuf and add lengths for non-blocking processing
> ------------------------------------------------------------------------
>                 Key: HADOOP-9421
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9421
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sanjay Radia
>            Assignee: Junping Du
>         Attachments: HADOOP-9421.patch, HADOOP-9421-v2-demo.patch

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message