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-37) Add OffsetSequencer
Date Wed, 09 Nov 2016 07:27:58 GMT

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

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

Github user sijie commented on the issue:

    https://github.com/apache/incubator-distributedlog/pull/15
  
    I am not sure if we should support this. I had the same feeling with @leighst - I don't
think we can find a reliable to use transaction id for offset.
    
    I am actually thinking in a different solution - we already have the length field for
each entry appended to bookkeeper ledger. we probably can just expose this length field to
the log segment metadata (like what we did for sequence id). so those length field can be
used as the offset for batch of records (aka entries). does that meet your requirement, @khurrumnasimm
? /cc @leighst 


> Add OffsetSequencer
> -------------------
>
>                 Key: DL-37
>                 URL: https://issues.apache.org/jira/browse/DL-37
>             Project: DistributedLog
>          Issue Type: Improvement
>          Components: distributedlog-core, distributedlog-service
>            Reporter: Khurrum Nasim
>            Assignee: Khurrum Nasim
>             Fix For: 0.4.0
>
>
> In order to support kafka like offset, we'd like to introduce an offset sequencer.



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

Mime
View raw message