[
https://issues.apache.org/jira/browse/RATIS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583104#comment-16583104
]
ASF GitHub Bot commented on RATIS-272:
--------------------------------------
GitHub user joshelser opened a pull request:
https://github.com/apache/incubator-ratis/pull/4
RATIS-272 logservice api
WIP. Based on Rajeshbabu's first API suggestions. Also adds:
* LogStream and LogService interfaces
* LogName to uniquely identify a LogStream in a LogService
* Listener (Tail) API for a LogStream
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/joshelser/incubator-ratis 272-logservice-api
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-ratis/pull/4.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 #4
----
commit 2a0465c06bdbe718824d6130426b352445b36f0a
Author: Josh Elser <elserj@...>
Date: 2018-08-16T16:34:23Z
RATIS-272 First wag at an API for the LogService
----
> Design ideal API
> ----------------
>
> Key: RATIS-272
> URL: https://issues.apache.org/jira/browse/RATIS-272
> Project: Ratis
> Issue Type: Sub-task
> Components: LogService
> Reporter: Josh Elser
> Priority: Major
>
> With influence from Apache DistributedLog, Kafka, and BookKeeper, design an
> API that balances the ideal notion of what a distribute log system should
> look like, but also considers the needs of HBase to replace a WAL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
