[
https://issues.apache.org/jira/browse/HBASE-12332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238899#comment-14238899
]
Jiajia Li commented on HBASE-12332:
-----------------------------------
hi, [~jmhsieh],
in reading, we don't directly open scanners to all the existing mob files which
is easy to know a file link by the matching the name pattern, instead we follow
steps below.
# Read the file name from the HBase ( this is just a file name, not a file link
pattern, we don't know the file link name in this cell).
# Read mob cell from the candidate paths( mobworkingDir/filename,
mobArchive/filename, the latter two are for cloned snapshot,
srcTableMobWorkingDir/filename, srcTableArchive/filename).
According to the above read path, it's not possible to know whether the current
mob file in the working directory is a file link by the name which is just a
mob file name (not a file link pattern).
In the latest patch, the possible read path had been reduced from 4 to 2 by
comparing the source table tag for the cloned snapshot. It means searching the
cloned snapshot is as fast as the normal mob cells.
Please advise. Thanks~
> [mob] use filelink instad of retry when resolving an hfilelink.
> ---------------------------------------------------------------
>
> Key: HBASE-12332
> URL: https://issues.apache.org/jira/browse/HBASE-12332
> Project: HBase
> Issue Type: Sub-task
> Components: mob
> Affects Versions: hbase-11339
> Reporter: Jonathan Hsieh
> Fix For: hbase-11339
>
> Attachments: HBASE-12332-V1.diff
>
>
> in the snapshot code, hmobstore was modified to traverse an hfile link to a
> mob. Ideally this should use the transparent filelink code to read the data.
> Also there will likely be some issues with the mob file cache with these
> links.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
