[
https://issues.apache.org/jira/browse/HBASE-21246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661097#comment-16661097
]
stack commented on HBASE-21246:
-------------------------------
bq. Through NoSuchLogException, we would consolidate WAL system error handling
with abstraction suitable for multiple WAL backends (Kafka, Distributed Log,
Ratis and distributed FileSystem). The handling of NoSuchLogException would
occur in no more than what current codebase handles FileNotFoundException.
i.e. every where we use a file.
What is this 'abstraction'?
bq. The thread beside the document provides background on how design decision
is reached.
Why then did we remove the many other threads but decide to keep this one? It
is confusing having both the doc and the thread. It makes the doc look like the
design is unresolved.
> Introduce WALIdentity interface
> -------------------------------
>
> Key: HBASE-21246
> URL: https://issues.apache.org/jira/browse/HBASE-21246
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Major
> Fix For: HBASE-20952
>
> Attachments: 21246.003.patch, 21246.HBASE-20952.001.patch,
> 21246.HBASE-20952.002.patch, 21246.HBASE-20952.004.patch,
> 21246.HBASE-20952.005.patch, 21246.HBASE-20952.007.patch,
> 21246.HBASE-20952.008.patch
>
>
> We are introducing WALIdentity interface so that the WAL representation can
> be decoupled from distributed filesystem.
> The interface provides getName method whose return value can represent
> filename in distributed filesystem environment or, the name of the stream
> when the WAL is backed by log stream.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
