[
https://issues.apache.org/jira/browse/DL-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15442271#comment-15442271
]
ASF GitHub Bot commented on DL-39:
----------------------------------
GitHub user jderrickk opened a pull request:
https://github.com/apache/incubator-distributedlog/pull/18
DL-39: Use a distributedlog uri to configure write proxy routing address
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jderrickk/incubator-distributedlog
jd/uri_resolver
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-distributedlog/pull/18.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #18
----
commit 7f266bf0dacec892c747fd01aaee67937dd6fee3
Author: Jon Derrick <[email protected]>
Date: 2016-08-25T07:20:01Z
Use a distributedlog uri to configure distributedlog client routing service
----
> Allow using distributed log uri for resolving the write proxy addresses
> -----------------------------------------------------------------------
>
> Key: DL-39
> URL: https://issues.apache.org/jira/browse/DL-39
> Project: DistributedLog
> Issue Type: Improvement
> Components: distributedlog-client
> Reporter: Jon Derrick
> Fix For: 0.4.0
>
>
> it is a bit inconvenient to configure the finagle name str for building
> clients. I have to construct myself by parsing the zkservers and path from
> the distributed log uri. it would be good that the client builder can accept
> the uri as resolver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
