[
https://issues.apache.org/jira/browse/RATIS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599202#comment-16599202
]
ASF GitHub Bot commented on RATIS-272:
--------------------------------------
Github user joshelser commented on the issue:
https://github.com/apache/incubator-ratis/pull/4
> C: Still think that adopting hierarchical naming scheme for log
directory is a right thing.
Let's keep this in mind as we work on the LogStream
administrative/management side. I think some hierarchy would make sense -- the
notion of a namespace to separate different LogStreams using the same "storage
directory" would be nice (DistributedLog has this concept).
Right now we just have a String (inside of `LogName`) to uniquely identify
one LogStream from another. This was intentional to let us either change how
`LogName`s compute uniqueness, or overlay some "logical" hierarchy using that
arbitrary String.
> 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)
