You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@distributedlog.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/05 09:41:58 UTC

[jira] [Commented] (DL-172) Provide a IDL definition for stream metadata and segment metadata

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

ASF GitHub Bot commented on DL-172:
-----------------------------------

GitHub user gerritsundaram opened a pull request:

    https://github.com/apache/incubator-distributedlog/pull/99

    DL-172: Provide a IDL definition for stream metadata and segment meta…

    https://issues.apache.org/jira/browse/DL-172

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gerritsundaram/incubator-distributedlog DL-73

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-distributedlog/pull/99.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 #99
    
----
commit c9224cb28e486c56a87f411f894e6bcab9d32b14
Author: Gerrit Sundaram <ge...@gmail.com>
Date:   2017-01-05T09:38:15Z

    DL-172: Provide a IDL definition for stream metadata and segment metadata

----


> Provide a IDL definition for stream metadata and segment metadata
> -----------------------------------------------------------------
>
>                 Key: DL-172
>                 URL: https://issues.apache.org/jira/browse/DL-172
>             Project: DistributedLog
>          Issue Type: New Feature
>          Components: distributedlog-protocol
>            Reporter: Gerrit Sundaram
>            Assignee: Gerrit Sundaram
>             Fix For: 0.5.0
>
>
> Currently there is not stream metadata structure and log segment metadata is a customized string structure. it would be good to use any IDL like thrift, protobuf to store the metadata like what bookkeeper is doing.
> The reason to choose protobuf is
> - because bookkeeper is using protobuf, it is okay to use same stuff.
> - the thrift version that DL is using is a bit too old and hard to bump because it seems the version is customized for finagle. using protobuf is easier to support other language clients.



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