distributedlog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DL-23) Move distributedlog build to depend on central maven repo
Date Wed, 09 Nov 2016 07:20:58 GMT

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

ASF GitHub Bot commented on DL-23:

Github user sijie commented on the issue:

    @leighst can you also take a look at this?
    I think it might be a good direction to go down to have a write-protocol specific client
or service. so it is easy to extend in future, like adding gRPC support and such.

> Move distributedlog build to depend on central maven repo
> ---------------------------------------------------------
>                 Key: DL-23
>                 URL: https://issues.apache.org/jira/browse/DL-23
>             Project: DistributedLog
>          Issue Type: Improvement
>          Components: distributedlog-client, distributedlog-core
>            Reporter: Sijie Guo
> Reported https://github.com/twitter/distributedlog/issues/37.
> Currently they are a few dependencies only exists at maven.twttr. There are two major
pieces, one is the finagle-serverset and while the other one is thrift library. The finagle-serverset
is majorly used for service-discovery by distributedlog-client and thrift is used by scrooge
and the rpc wire protocol between client and write proxy.
> There are two options:
> - one is to look for a solution to move those dependencies to central maven repo.
> - the other one is to see if we can make thrift and its service discovery pluginnable.
so we can support both finagle-thrift and gRPC-protobuf. 

This message was sent by Atlassian JIRA

View raw message