[
https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412165#comment-15412165
]
Sai Teja Ranuva commented on HBASE-16148:
-----------------------------------------
Thank you Enis. I feel the second approach may not be friendly to the client
and also it will give a way for client to manipulate with server clock(not sure
if it is bad thing, but sounds like it could be exploited adversely). I will
try to find a way to differentiate between client set timestamps to that of
replication/wal recovery as you suggested.
> Hybrid Logical Clocks(placeholder for running tests)
> ----------------------------------------------------
>
> Key: HBASE-16148
> URL: https://issues.apache.org/jira/browse/HBASE-16148
> Project: HBase
> Issue Type: Sub-task
> Components: API
> Reporter: Sai Teja Ranuva
> Assignee: Sai Teja Ranuva
> Priority: Minor
> Labels: test-patch
> Attachments: HBASE-16148.master.001.patch,
> HBASE-16148.master.6.patch, HBASE-16148.master.test.1.patch,
> HBASE-16148.master.test.2.patch, HBASE-16148.master.test.3.patch,
> HBASE-16148.master.test.4.patch, HBASE-16148.master.test.5.patch,
> HLC.1.patch, HLC.2.patch, HLC.patch
>
>
> This JIRA is just a placeholder to test Hybrid Logical Clocks code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
