[
https://issues.apache.org/jira/browse/RATIS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599182#comment-16599182
]
ASF GitHub Bot commented on RATIS-272:
--------------------------------------
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/incubator-ratis/pull/4#discussion_r214453065
--- Diff:
ratis-logservice/src/main/java/org/apache/ratis/logservice/api/LogStreamConfiguration.java
---
@@ -0,0 +1,47 @@
+package org.apache.ratis.logservice.api;
+
+import java.util.Map;
+import java.util.Map.Entry;
+
+/**
+ * An encapsulation of configuration for a LogStream.
+ */
+public interface LogStreamConfiguration {
--- End diff --
I definitely don't want to reuse Hadoop's Configuration because
hadoop-common pulls in tons of crap we don't want or need just to reuse
Configuration. Ratis does have the notion of configuration, but I see this
object sitting on top of that. The RaftClient has configuration controls how
that would be set up, but the LogService would have more on top of that.
My goal was to just keep this as minimal as possible and only using
JRE-provided classes until we have a better idea of how we'll use the
configuration.
> 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)
