You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/01/19 00:42:00 UTC

[jira] [Resolved] (KUDU-2228) Make Messenger options configurable

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

Todd Lipcon resolved KUDU-2228.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

Sailesh fixed in b357fa9b729ce52627a862e08ebac822ae470bc9

> Make Messenger options configurable
> -----------------------------------
>
>                 Key: KUDU-2228
>                 URL: https://issues.apache.org/jira/browse/KUDU-2228
>             Project: Kudu
>          Issue Type: Task
>          Components: rpc
>            Reporter: Sailesh Mukil
>            Assignee: Sailesh Mukil
>            Priority: Major
>              Labels: refactor, rpc
>             Fix For: 1.7.0
>
>
> Currently, the RPC layer accesses many gflags directly to take certain decisions, eg. whether to turn on encryption, authentication, etc.
> Since the RPC layer is to be used more like a library, these should be configurable options that are passed to the Messenger (which is the API endpoint for the application using the RPC layer), instead of the RPC layer itself directly accessing these flags.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)