[
https://issues.apache.org/jira/browse/HBASE-21246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651955#comment-16651955
]
Josh Elser commented on HBASE-21246:
------------------------------------
Just noticed I had this pending.. sorry for the delay:
{quote}I can create a WALIdentity and it has no associated WAL instance? So
we'd build handling for case where we are passed a WALIdentity with no
associated WAL? So lots of NoSuchWALIDExceptions on the API?
{quote}
I don't _think_ this would have to be any worse than we have it today with
{{Path}}. The way we do FS-based WALs pushes us towards that, but we can
certainly push back. We could get rid of the notion entirely and just pass
around a WAL instead. More impact on the codebase, but it would alleviate you
problem you point out (at least most of them). This might be something worth
investigating.
> 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
>
>
> 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)
