[jira] [Created] (HBASE-16605) Removal of Master System Time from Admin protos for 2.0
Sai Teja Ranuva created HBASE-16605: --- Summary: Removal of Master System Time from Admin protos for 2.0 Key: HBASE-16605 URL: https://issues.apache.org/jira/browse/HBASE-16605 Project: HBase Issue Type: Task Affects Versions: 2.0.0 Reporter: Sai Teja Ranuva Assignee: Matteo Bertozzi In HBase 2.0, everything that uses Master System Time is supposed to be moved to Master. If all of that work is completed, then Master System Time field in the Admin Protos can be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15478593#comment-15478593 ] Sai Teja Ranuva edited comment on HBASE-14070 at 9/9/16 11:53 PM: -- The patch - HBase-14070.master.001.patch contains the current unfinished changes for the HLC project. A document describing current state of the work and work yet to be done is attached in the HBASE-14070. It is present in the links section of this JIRA, it is named Current Status of HLC. Work Done: Timestamp Enum Class with all the methods with the tests Clock Class supporting three clock types with the tests HLC clock updates during recovery and replication Clock per Region Server notion TTL and Time to Purge work well across all Clock Types Most of the time related tests are parameterized to run against all the three clock types. Test cases setting timestamps in Put were changed so that timestamp is not set with the help of manual environment edge The tests were run with HLC as default clock type of the tables and most of the bugs have been removed. There is still some work to be done to get all the tests passed. Work Yet to done: Time range should be dealt with as per section 3.3 A check, for HLC and System Monotonic tables, disallowing clients to set the timestamps in the server side and not on the client side (Keep Client dumb) Currently, still some test cases are flaky, some are failing. Need to clear them. HLC clock should be updates for more events such open, close regions etc. as per various use cases. Deciding which events we should track is important. Bulk Loads need to be thought upon. Mechanism to ensure that the bulk loaded files are having correct timestamp types. If we can have the highest timestamp of all the cells, we can update the local clock with it. This is something to think about. Test cases written currently are very local, need to write some integration tests which tests the HLC clock properties w.r.t recovery, replication and more. Currently some of the tests were rewritten using manual environment edge to get around the problem of not setting timestamps for HLC tables. A suggestion was made by Stack and Enis to not use environment edge in the clocks. Instead have a pluggable manual clock in place of Environment Edge. was (Author: saitejar): The patch - HBase-14070.master.001.patch contains the current unfinished changes for the HLC project. A document describing current state of the work and work yet to be done is attached in the HBASE-14070. To summarise it: Work Done: Timestamp Enum Class with all the methods with the tests Clock Class supporting three clock types with the tests HLC clock updates during recovery and replication Clock per Region Server notion TTL and Time to Purge work well across all Clock Types Most of the time related tests are parameterized to run against all the three clock types. Test cases setting timestamps in Put were changed so that timestamp is not set with the help of manual environment edge The tests were run with HLC as default clock type of the tables and most of the bugs have been removed. There is still some work to be done to get all the tests passed. Work Yet to done: Time range should be dealt with as per section 3.3 A check, for HLC and System Monotonic tables, disallowing clients to set the timestamps in the server side and not on the client side (Keep Client dumb) Currently, still some test cases are flaky, some are failing. Need to clear them. HLC clock should be updates for more events such open, close regions etc. as per various use cases. Deciding which events we should track is important. Bulk Loads need to be thought upon. Mechanism to ensure that the bulk loaded files are having correct timestamp types. If we can have the highest timestamp of all the cells, we can update the local clock with it. This is something to think about. Test cases written currently are very local, need to write some integration tests which tests the HLC clock properties w.r.t recovery, replication and more. Currently some of the tests were rewritten using manual environment edge to get around the problem of not setting timestamps for HLC tables. A suggestion was made by Stack and Enis to not use environment edge in the clocks. Instead have a pluggable manual clock in place of Environment Edge. > Hybrid Logical Clocks for HBase > --- > > Key: HBASE-14070 > URL: https://issues.apache.org/jira/browse/HBASE-14070 > Project: HBase > Issue Type: New Feature >Reporter: Enis Soztutar >Assignee: Sai Teja Ranuva > Attachments: HBASE-14070.master.001.patch, > HybridLogicalClocksforHBaseandPhoenix.docx, > HybridLogicalClocksforHBaseandPhoenix.pdf > > > HBase and Phoenix uses systems physical clock (PT) to give timestamps
[jira] [Comment Edited] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15478493#comment-15478493 ] Sai Teja Ranuva edited comment on HBASE-14070 at 9/9/16 11:13 PM: -- The document(Current Status of HLC - google doc) contains the current status of the project with some details of the decisions made in the process. It also contains the work that is yet to be done. Open to comments. was (Author: saitejar): This document contains the current status of the project with some details of the decisions made in the process. It also contains the work that is yet to be done. > Hybrid Logical Clocks for HBase > --- > > Key: HBASE-14070 > URL: https://issues.apache.org/jira/browse/HBASE-14070 > Project: HBase > Issue Type: New Feature >Reporter: Enis Soztutar >Assignee: Sai Teja Ranuva > Attachments: HBASE-14070.master.001.patch, > HybridLogicalClocksforHBaseandPhoenix.docx, > HybridLogicalClocksforHBaseandPhoenix.pdf > > > HBase and Phoenix uses systems physical clock (PT) to give timestamps to > events (read and writes). This works mostly when the system clock is strictly > monotonically increasing and there is no cross-dependency between servers > clocks. However we know that leap seconds, general clock skew and clock drift > are in fact real. > This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of > hybrid physical clock + a logical clock. HLC is best of both worlds where it > keeps causality relationship similar to logical clocks, but still is > compatible with NTP based physical system clock. HLC can be represented in > 64bits. > A design document is attached and also can be found here: > https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15478593#comment-15478593 ] Sai Teja Ranuva commented on HBASE-14070: - The patch - HBase-14070.master.001.patch contains the current unfinished changes for the HLC project. A document describing current state of the work and work yet to be done is attached in the HBASE-14070. To summarise it: Work Done: Timestamp Enum Class with all the methods with the tests Clock Class supporting three clock types with the tests HLC clock updates during recovery and replication Clock per Region Server notion TTL and Time to Purge work well across all Clock Types Most of the time related tests are parameterized to run against all the three clock types. Test cases setting timestamps in Put were changed so that timestamp is not set with the help of manual environment edge The tests were run with HLC as default clock type of the tables and most of the bugs have been removed. There is still some work to be done to get all the tests passed. Work Yet to done: Time range should be dealt with as per section 3.3 A check, for HLC and System Monotonic tables, disallowing clients to set the timestamps in the server side and not on the client side (Keep Client dumb) Currently, still some test cases are flaky, some are failing. Need to clear them. HLC clock should be updates for more events such open, close regions etc. as per various use cases. Deciding which events we should track is important. Bulk Loads need to be thought upon. Mechanism to ensure that the bulk loaded files are having correct timestamp types. If we can have the highest timestamp of all the cells, we can update the local clock with it. This is something to think about. Test cases written currently are very local, need to write some integration tests which tests the HLC clock properties w.r.t recovery, replication and more. Currently some of the tests were rewritten using manual environment edge to get around the problem of not setting timestamps for HLC tables. A suggestion was made by Stack and Enis to not use environment edge in the clocks. Instead have a pluggable manual clock in place of Environment Edge. > Hybrid Logical Clocks for HBase > --- > > Key: HBASE-14070 > URL: https://issues.apache.org/jira/browse/HBASE-14070 > Project: HBase > Issue Type: New Feature >Reporter: Enis Soztutar >Assignee: Sai Teja Ranuva > Attachments: HBASE-14070.master.001.patch, > HybridLogicalClocksforHBaseandPhoenix.docx, > HybridLogicalClocksforHBaseandPhoenix.pdf > > > HBase and Phoenix uses systems physical clock (PT) to give timestamps to > events (read and writes). This works mostly when the system clock is strictly > monotonically increasing and there is no cross-dependency between servers > clocks. However we know that leap seconds, general clock skew and clock drift > are in fact real. > This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of > hybrid physical clock + a logical clock. HLC is best of both worlds where it > keeps causality relationship similar to logical clocks, but still is > compatible with NTP based physical system clock. HLC can be represented in > 64bits. > A design document is attached and also can be found here: > https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-14070: Attachment: HBASE-14070.master.001.patch > Hybrid Logical Clocks for HBase > --- > > Key: HBASE-14070 > URL: https://issues.apache.org/jira/browse/HBASE-14070 > Project: HBase > Issue Type: New Feature >Reporter: Enis Soztutar >Assignee: Sai Teja Ranuva > Attachments: HBASE-14070.master.001.patch, > HybridLogicalClocksforHBaseandPhoenix.docx, > HybridLogicalClocksforHBaseandPhoenix.pdf > > > HBase and Phoenix uses systems physical clock (PT) to give timestamps to > events (read and writes). This works mostly when the system clock is strictly > monotonically increasing and there is no cross-dependency between servers > clocks. However we know that leap seconds, general clock skew and clock drift > are in fact real. > This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of > hybrid physical clock + a logical clock. HLC is best of both worlds where it > keeps causality relationship similar to logical clocks, but still is > compatible with NTP based physical system clock. HLC can be represented in > 64bits. > A design document is attached and also can be found here: > https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.10.7.patch Commented TestReplicationStatus to check if any other tests failing. TestReplicationStatus is passing locally. > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.10.1.patch, HLC.10.2.patch, > HLC.10.3.patch, HLC.10.4.patch, HLC.10.5.patch, HLC.10.6.patch, > HLC.10.7.patch, HLC.10.patch, HLC.2.patch, HLC.3.patch, HLC.4.patch, > HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.10.5.patch Bugs found in TTL, timetopurge removed. Parameterized other failed tests, changed to include HLC clock, System Monotonic. > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.10.1.patch, HLC.10.2.patch, > HLC.10.3.patch, HLC.10.4.patch, HLC.10.5.patch, HLC.10.patch, HLC.2.patch, > HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.10.3.patch Removed TTL related Bugs. > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.10.1.patch, HLC.10.2.patch, > HLC.10.3.patch, HLC.10.patch, HLC.2.patch, HLC.3.patch, HLC.4.patch, > HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.10.2.patch made Heap Size correction for HRegion Class for newly added reference to the Clock in the class. (failed test - testSizes in testHeapSize.java) > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.10.1.patch, HLC.10.2.patch, > HLC.10.patch, HLC.2.patch, HLC.3.patch, HLC.4.patch, HLC.5.patch, > HLC.6.patch, HLC.8.patch, HLC.9.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.10.1.patch Removed stray import error present in HLC.10.patch. Essentially same as HLC.10 i.e "Worked on removing test case failures of HLC.9.patch, parameterized some tests to run for all three clocks." > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.10.1.patch, HLC.10.patch, > HLC.2.patch, HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, > HLC.9.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.10.patch Worked on removing test case failures, parameterized some tests to run for all three clocks. > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.10.patch, HLC.2.patch, > HLC.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.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)
[jira] [Commented] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439481#comment-15439481 ] Sai Teja Ranuva commented on HBASE-16504: - By preserving the timestamp, I meant the put timestamp during replication. But it looks like it is not used/useful anywhere. There is already a check for the cell timestamps(i.e complete replicated cell is matched, so all dimensions are taken care). If we plan to carry forward the put timestamp during replication too, then we need to add a test case to check it. > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: question, replication > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16504: Comment: was deleted (was: With respect to preserving the timestamp, I meant the put timestamp during replication. But it looks like it is not used/useful anywhere.) > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: question, replication > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15439474#comment-15439474 ] Sai Teja Ranuva commented on HBASE-16504: - With respect to preserving the timestamp, I meant the put timestamp during replication. But it looks like it is not used/useful anywhere. > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: question, replication > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16504: Labels: question replication (was: replication replication-testing) > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: question, replication > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva resolved HBASE-16504. - Resolution: Not A Problem Assignee: Sai Teja Ranuva The timestamp of the mutation is not useful as the cells already have their timestamp set at the time of replication. In detail: Normally, if the cells do not have their timestamp set, put/delete timestamp is used instead, when it is LATEST_TIMESTAMP, server time is used. This flow doesn't happen in case of replication, as we need not look outside of the cell to get timestamp. > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16504: Flags: (was: Important) > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Priority: Minor > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438520#comment-15438520 ] Sai Teja Ranuva commented on HBASE-16504: - Thanks Phil, I think everything makes more sense to me now. For the case of replication, the cells will already have a timestamp set, so the put timestamp is of no use. > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Priority: Minor > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16504: Priority: Minor (was: Major) > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva >Priority: Minor > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438511#comment-15438511 ] Sai Teja Ranuva edited comment on HBASE-16504 at 8/26/16 5:53 AM: -- Okay.. I think I got your point. So, what is the purpose of the Put timestamp ? was (Author: saitejar): Okay.. I think got your point. So, what is the purpose of the Put timestamp ? > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438511#comment-15438511 ] Sai Teja Ranuva commented on HBASE-16504: - Okay.. I think got your point. So, what is the purpose of the Put timestamp ? > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16504) Replication is not preserving the timestamp of the cell
[ https://issues.apache.org/jira/browse/HBASE-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15438458#comment-15438458 ] Sai Teja Ranuva commented on HBASE-16504: - Hi Phil I ran debugger to check if the timestamp changes after running through the code you mentioned. The timestamp remains the same(i.e HConstants.LATEST_TIMESTAMP). Most probably even the above code is not copying the timestamp from the cell. - Sai > Replication is not preserving the timestamp of the cell > --- > > Key: HBASE-16504 > URL: https://issues.apache.org/jira/browse/HBASE-16504 > Project: HBase > Issue Type: Bug > Components: Replication >Reporter: Sai Teja Ranuva > Labels: replication, replication-testing > > The Replication procedure in ReplicationSink.replicateEntries() method is not > preserving the timestamp of the cell. > Pointer to the code: > m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), > cell.getRowOffset(),cell.getRowLength()); > The Put and Delete constructors called here assign the timestamp with > HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the > cell here. > Also there doesn't seem to be a test which checks if replication is > preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16504) Replication is not preserving the timestamp of the cell
Sai Teja Ranuva created HBASE-16504: --- Summary: Replication is not preserving the timestamp of the cell Key: HBASE-16504 URL: https://issues.apache.org/jira/browse/HBASE-16504 Project: HBase Issue Type: Bug Components: Replication Reporter: Sai Teja Ranuva The Replication procedure in ReplicationSink.replicateEntries() method is not preserving the timestamp of the cell. Pointer to the code: m = CellUtil.isDelete(cell) ? new Delete(cell.getRowArray(), cell.getRowOffset(),cell.getRowLength()) : new Put(cell.getRowArray(), cell.getRowOffset(),cell.getRowLength()); The Put and Delete constructors called here assign the timestamp with HConstants.LATEST_TIMESTAMP. Instead we need to keep the timestamp of the cell here. Also there doesn't seem to be a test which checks if replication is preserving the timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.9.patch Patch to check for failed tests with HLC as default. Corrected Failing tests in previous patch. Small Tests not failing locally. > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.patch, HLC.9.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.8.patch Made HLC default clock type of all tables. Added Clock updates for recovery and replication. Patch to check the dependency of clock type in the test cases. (Corrected the rebase error) > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: (was: HLC.8.patch) > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.8.patch Made HLC default clock type of tables. Added Clock updates for recovery and replication. Patch to check the dependency of clock type in the test cases. > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.patch, HLC.8.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.004.patch > 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.002.patch, HBASE-16148.master.003.patch, > HBASE-16148.master.004.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.003.patch > 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.002.patch, HBASE-16148.master.003.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.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421535#comment-15421535 ] Sai Teja Ranuva commented on HBASE-16148: - [~stack] THank you for the suggestion. Yes, I will use the tool from now on. I should have described changes for all patches. Should all patches be posted up to RB ? > 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.002.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.002.patch > 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.002.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.3.patch, > HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.6.patch > 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.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.3.patch, HLC.4.patch, HLC.5.patch, HLC.6.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.3.patch, HLC.4.patch, HLC.5.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.3.patch, HLC.4.patch, HLC.5.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.5.patch > 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.3.patch, HLC.4.patch, HLC.5.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.3.patch, HLC.4.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.4.patch > 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.3.patch, HLC.4.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.3.patch, HLC.4.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.3.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.3.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.3.patch > 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.3.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)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: (was: HLC.3.patch) > 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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.3.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.3.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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.3.patch > 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.3.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)
[jira] [Issue Comment Deleted] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Comment: was deleted (was: [~enis] Referring to the RB link, in the to do list, you have written. "Puts with client-set timestamps should update the clocks." Should we update the server clock with client set timestamps ? In HBase, client can set any timestamp he wants, it could have any skew. I feel we should not update the clock with client set timestamps, rather send another field in put request which just reads time of system clock, use that to update server clock. ) > 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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.2.patch > 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)
[jira] [Commented] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409853#comment-15409853 ] Sai Teja Ranuva commented on HBASE-16148: - [~enis] Referring to the RB link, in the to do list, you have written. "Puts with client-set timestamps should update the clocks." Should we update the server clock with client set timestamps ? In HBase, client can set any timestamp he wants, it could have any skew. I feel we should not update the clock with client set timestamps, rather send another field in put request which just reads time of system clock, use that to update server clock. > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.1.patch > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HLC.patch > 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.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.6.patch HLC patch, testing. > 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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-16285) Drop RPC requests if it must be considered as timeout at client
[ https://issues.apache.org/jira/browse/HBASE-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400320#comment-15400320 ] Sai Teja Ranuva edited comment on HBASE-16285 at 7/30/16 1:06 AM: -- It would be great if the rationale behind choosing 200ms or 50ms for DEAFAULT_DROP_TIMEOUT_REQUEST_DELAY is put in the comments for future reference. was (Author: saitejar): It would be great if the rationale behind choosing 200ms(or 50ms as suggested by [~stack]) for DEAFAULT_DROP_TIMEOUT_REQUEST_DELAY is put in the comments for future reference. > Drop RPC requests if it must be considered as timeout at client > --- > > Key: HBASE-16285 > URL: https://issues.apache.org/jira/browse/HBASE-16285 > Project: HBase > Issue Type: Improvement >Reporter: Phil Yang >Assignee: Phil Yang > Attachments: HBASE-16285-branch-1-v1.patch, HBASE-16285-v1.patch > > > After HBASE-15593, we have a timeout param in header of RPC requests. We can > use it in more scenes. > A straightforward scene is to drop requests if it has waited so long in RPC > queue and has been dropped by client. Even if we handle this request and send > the response back, it will not be used any more. And client may have sent a > retry. In an extreme case, if the server is slow, all requests may be timeout > or queue-full-exception because we should handle previous requests which have > been dropped by client and many resources at server are wasted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16285) Drop RPC requests if it must be considered as timeout at client
[ https://issues.apache.org/jira/browse/HBASE-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400320#comment-15400320 ] Sai Teja Ranuva commented on HBASE-16285: - It would be great if the rationale behind choosing 200ms(or 50ms as suggested by [~stack]) for DEAFAULT_DROP_TIMEOUT_REQUEST_DELAY is put in the comments for future reference. > Drop RPC requests if it must be considered as timeout at client > --- > > Key: HBASE-16285 > URL: https://issues.apache.org/jira/browse/HBASE-16285 > Project: HBase > Issue Type: Improvement >Reporter: Phil Yang >Assignee: Phil Yang > Attachments: HBASE-16285-branch-1-v1.patch, HBASE-16285-v1.patch > > > After HBASE-15593, we have a timeout param in header of RPC requests. We can > use it in more scenes. > A straightforward scene is to drop requests if it has waited so long in RPC > queue and has been dropped by client. Even if we handle this request and send > the response back, it will not be used any more. And client may have sent a > retry. In an extreme case, if the server is slow, all requests may be timeout > or queue-full-exception because we should handle previous requests which have > been dropped by client and many resources at server are wasted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399966#comment-15399966 ] Sai Teja Ranuva edited comment on HBASE-16148 at 7/29/16 8:37 PM: -- remove setting of timestamp in meta table accessor to mutate meta table. was (Author: saitejar): remove setting of timestamp by master to mutate meta table. > 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.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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.test.5.patch remove setting of timestamp by master to mutate meta table. > 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.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 > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16306) Add specific imports to avoid namespace clash in defaultSource.scala
[ https://issues.apache.org/jira/browse/HBASE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16306: Description: I am working on adding Hybrid Logical clocks to HBase. As part of it, I wish to add TimestampType file in hbase common. Spark has some types defined in - org.apache.spark.sql.types, all of which are being imported. It also has a TimestampType defined. As currently in this file, all of the hbase common is imported, creating a namespace clash. I have changed to only import specific hbase common classes that are required in this file. (was: I am working on adding Hybrid Logical clocks to HBase. As part of it, I wish to add TimestampType file in hbase common. Spark has some types defined in - org.apache.spark.sql.types, all of which are being imported. It also has a TimestampType defined. As currently in this file, all of the hbase common is imported, creating a namespace clash. I have changed to imports to only specific hbase common classes that are required in this file.) > Add specific imports to avoid namespace clash in defaultSource.scala > > > Key: HBASE-16306 > URL: https://issues.apache.org/jira/browse/HBASE-16306 > Project: HBase > Issue Type: Bug >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Attachments: HBASE-16306.master.1.patch > > > I am working on adding Hybrid Logical clocks to HBase. As part of it, I wish > to add TimestampType file in hbase common. Spark has some types defined in - > org.apache.spark.sql.types, all of which are being imported. It also has a > TimestampType defined. As currently in this file, all of the hbase common is > imported, creating a namespace clash. I have changed to only import specific > hbase common classes that are required in this file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16306) Add specific imports to avoid namespace clash in defaultSource.scala
[ https://issues.apache.org/jira/browse/HBASE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16306: Attachment: HBASE-16306.master.1.patch > Add specific imports to avoid namespace clash in defaultSource.scala > > > Key: HBASE-16306 > URL: https://issues.apache.org/jira/browse/HBASE-16306 > Project: HBase > Issue Type: Bug >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Attachments: HBASE-16306.master.1.patch > > > I am working on adding Hybrid Logical clocks to HBase. As part of it, I wish > to add TimestampType file in hbase common. Spark has some types defined in - > org.apache.spark.sql.types, all of which are being imported. It also has a > TimestampType defined. As currently in this file, all of the hbase common is > imported, creating a namespace clash. I have changed to imports to only > specific hbase common classes that are required in this file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16306) Add specific imports to avoid namespace clash in defaultSource.scala
[ https://issues.apache.org/jira/browse/HBASE-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16306: Status: Patch Available (was: Open) > Add specific imports to avoid namespace clash in defaultSource.scala > > > Key: HBASE-16306 > URL: https://issues.apache.org/jira/browse/HBASE-16306 > Project: HBase > Issue Type: Bug >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Attachments: HBASE-16306.master.1.patch > > > I am working on adding Hybrid Logical clocks to HBase. As part of it, I wish > to add TimestampType file in hbase common. Spark has some types defined in - > org.apache.spark.sql.types, all of which are being imported. It also has a > TimestampType defined. As currently in this file, all of the hbase common is > imported, creating a namespace clash. I have changed to imports to only > specific hbase common classes that are required in this file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16306) Add specific imports to avoid namespace clash in defaultSource.scala
Sai Teja Ranuva created HBASE-16306: --- Summary: Add specific imports to avoid namespace clash in defaultSource.scala Key: HBASE-16306 URL: https://issues.apache.org/jira/browse/HBASE-16306 Project: HBase Issue Type: Bug Reporter: Sai Teja Ranuva Assignee: Sai Teja Ranuva Priority: Minor I am working on adding Hybrid Logical clocks to HBase. As part of it, I wish to add TimestampType file in hbase common. Spark has some types defined in - org.apache.spark.sql.types, all of which are being imported. It also has a TimestampType defined. As currently in this file, all of the hbase common is imported, creating a namespace clash. I have changed to imports to only specific hbase common classes that are required in this file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Status: Patch Available (was: Open) > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch, HBASE-16256.master.2.patch, > HBASE-16256.master.3.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Status: Open (was: Patch Available) > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch, HBASE-16256.master.2.patch, > HBASE-16256.master.3.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Attachment: HBASE-16256.master.3.patch Formatted the class doc to appear properly when javadoc is generated. > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch, HBASE-16256.master.2.patch, > HBASE-16256.master.3.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Status: Open (was: Patch Available) > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch, HBASE-16256.master.2.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Status: Patch Available (was: Open) > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch, HBASE-16256.master.2.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16297) Sub task of HBASE-15041 - To clear javadoc errors in Client Module.
[ https://issues.apache.org/jira/browse/HBASE-16297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16297: Issue Type: Sub-task (was: Improvement) Parent: HBASE-15041 > Sub task of HBASE-15041 - To clear javadoc errors in Client Module. > --- > > Key: HBASE-16297 > URL: https://issues.apache.org/jira/browse/HBASE-16297 > Project: HBase > Issue Type: Sub-task >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: documentation > > This issue is to fix the javadoc errors in client module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16297) Sub task of HBASE-15041 - To clear javadoc errors in Client Module.
Sai Teja Ranuva created HBASE-16297: --- Summary: Sub task of HBASE-15041 - To clear javadoc errors in Client Module. Key: HBASE-16297 URL: https://issues.apache.org/jira/browse/HBASE-16297 Project: HBase Issue Type: Improvement Reporter: Sai Teja Ranuva Assignee: Sai Teja Ranuva Priority: Minor This issue is to fix the javadoc errors in client module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Attachment: HBASE-16256.master.1.patch Added the purpose of the Environment Edge Manager to the class doc. The reasons why it is not being used for the purpose it was designed for currently. > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16256) Purpose of EnvironmentEdge, EnvironmentEdgeManager
[ https://issues.apache.org/jira/browse/HBASE-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16256: Status: Patch Available (was: Open) > Purpose of EnvironmentEdge, EnvironmentEdgeManager > -- > > Key: HBASE-16256 > URL: https://issues.apache.org/jira/browse/HBASE-16256 > Project: HBase > Issue Type: Improvement > Components: documentation, regionserver >Reporter: Sai Teja Ranuva >Priority: Trivial > Labels: beginner, clarification > Fix For: 2.0.0 > > Attachments: HBASE-16256.master.1.patch > > > I am trying to figure out the purpose of EnvironmentEdge in the HBase code. > The java doc says it has something to do with environment, I feel it is > vague. It looks like there is a bigger picture for such a design. Currently > only concrete method that is available in it is currentTime(). > Can anyone summarize the rationale behind having > EnvironmentEdge/EnvironmentEdgeManager ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.test.4.patch > 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.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch, HBASE-16148.master.test.4.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch, HBASE-16148.master.test.4.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch, HBASE-16148.master.test.4.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.test.3.patch > 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.test.1.patch, HBASE-16148.master.test.2.patch, > HBASE-16148.master.test.3.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.test.1.patch, HBASE-16148.master.test.2.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.test.1.patch, HBASE-16148.master.test.2.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.test.2.patch > 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.test.1.patch, HBASE-16148.master.test.2.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Open (was: Patch Available) > 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.test.1.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Status: Patch Available (was: Open) > 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.test.1.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16148) Hybrid Logical Clocks(placeholder for running tests)
[ https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16148: Attachment: HBASE-16148.master.test.1.patch > 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.test.1.patch > > > This JIRA is just a placeholder to test Hybrid Logical Clocks code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-16210) Add Timestamp class to the hbase-common
[ https://issues.apache.org/jira/browse/HBASE-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15388317#comment-15388317 ] Sai Teja Ranuva commented on HBASE-16210: - Yes :), that is right, you expressed it perfectly. [~stack] > Add Timestamp class to the hbase-common > --- > > Key: HBASE-16210 > URL: https://issues.apache.org/jira/browse/HBASE-16210 > Project: HBase > Issue Type: Sub-task >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: patch, testing > Attachments: HBASE-16210.master.1.patch, HBASE-16210.master.2.patch, > HBASE-16210.master.3.patch, HBASE-16210.master.4.patch, > HBASE-16210.master.5.patch, HBASE-16210.master.6.patch, > HBASE-16210.master.7.patch, HBASE-16210.master.8.1.patch, > HBASE-16210.master.8.2.patch, HBASE-16210.master.8.3.patch, > HBASE-16210.master.8.4.patch, HBASE-16210.master.8.patch > > > This is a sub-issue of > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070]. This JIRA is > a small step towards completely adding Hybrid Logical Clocks(HLC) to HBase. > The main idea of HLC is described in > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070] along with > the motivation of adding it to HBase. > This patch in this issue takes the code from the patch in the parent. > The parent patch is pretty big to review at once. So, plan is to get code > reviewed in smaller patches and > in the process take suggestions and change things if necessary. > What is this patch/issue about ? > This issue attempts to add a timestamp class to hbase-common and timestamp > type to HTable. > This is a part of the attempt to get HLC into HBase. This patch does not > interfere with the current working of HBase. > Why Timestamp Class ? > Timestamp class can be as an abstraction to represent time in Hbase in 64 > bits. > It is just used for manipulating with the 64 bits of the timestamp and is not > concerned about the actual time. > There are three types of timestamps. System time, Custom and HLC. Each one of > it has methods to manipulate the 64 bits of timestamp. > HTable changes: Added a timestamp type property to HTable. This will help > HBase exist in conjunction with old type of timestamp and also the HLC which > will be introduced. The default is set to custom timestamp(current way of > usage of timestamp). default unset timestamp is also custom timestamp as it > should be so. The default timestamp will be changed to HLC when HLC feature > is introduced completely in HBase. > Check HBASE-16210.master.6.patch. > Update: Based on the suggestions, made timestamp enum. Here is the > description of the new changes. > Check the HBASE-16210.master.8.1.patch > 1. Changed the Timestamp Implementation to Enum. > 2. Changed the Timestamp semantics. Instead of HLC, System monotonic and > custom, we now have Hybrid and Physical. System monotonic clock and Custom > clocks can map their timestamps to Physical. HLC clock can map its timestamp > to Hybrid. > 3. The HTableDescriptor will contain clock type(not implemented yet) instead > of timestamp type. As clocks convey the semantics of monotonic increasing and > non decreasing etc. TimestampType doesn't have those semantics enforced, it > just knows what to do with given 64 bits. Therefore, I removed the timestamp > type field in the HTableDescriptor. > Open for suggestions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16210) Add Timestamp class to the hbase-common
[ https://issues.apache.org/jira/browse/HBASE-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16210: Attachment: HBASE-16210.master.8.4.patch > Add Timestamp class to the hbase-common > --- > > Key: HBASE-16210 > URL: https://issues.apache.org/jira/browse/HBASE-16210 > Project: HBase > Issue Type: Sub-task >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: patch, testing > Attachments: HBASE-16210.master.1.patch, HBASE-16210.master.2.patch, > HBASE-16210.master.3.patch, HBASE-16210.master.4.patch, > HBASE-16210.master.5.patch, HBASE-16210.master.6.patch, > HBASE-16210.master.7.patch, HBASE-16210.master.8.1.patch, > HBASE-16210.master.8.2.patch, HBASE-16210.master.8.3.patch, > HBASE-16210.master.8.4.patch, HBASE-16210.master.8.patch > > > This is a sub-issue of > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070]. This JIRA is > a small step towards completely adding Hybrid Logical Clocks(HLC) to HBase. > The main idea of HLC is described in > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070] along with > the motivation of adding it to HBase. > This patch in this issue takes the code from the patch in the parent. > The parent patch is pretty big to review at once. So, plan is to get code > reviewed in smaller patches and > in the process take suggestions and change things if necessary. > What is this patch/issue about ? > This issue attempts to add a timestamp class to hbase-common and timestamp > type to HTable. > This is a part of the attempt to get HLC into HBase. This patch does not > interfere with the current working of HBase. > Why Timestamp Class ? > Timestamp class can be as an abstraction to represent time in Hbase in 64 > bits. > It is just used for manipulating with the 64 bits of the timestamp and is not > concerned about the actual time. > There are three types of timestamps. System time, Custom and HLC. Each one of > it has methods to manipulate the 64 bits of timestamp. > HTable changes: Added a timestamp type property to HTable. This will help > HBase exist in conjunction with old type of timestamp and also the HLC which > will be introduced. The default is set to custom timestamp(current way of > usage of timestamp). default unset timestamp is also custom timestamp as it > should be so. The default timestamp will be changed to HLC when HLC feature > is introduced completely in HBase. > Check HBASE-16210.master.6.patch. > Update: Based on the suggestions, made timestamp enum. Here is the > description of the new changes. > Check the HBASE-16210.master.8.1.patch > 1. Changed the Timestamp Implementation to Enum. > 2. Changed the Timestamp semantics. Instead of HLC, System monotonic and > custom, we now have Hybrid and Physical. System monotonic clock and Custom > clocks can map their timestamps to Physical. HLC clock can map its timestamp > to Hybrid. > 3. The HTableDescriptor will contain clock type(not implemented yet) instead > of timestamp type. As clocks convey the semantics of monotonic increasing and > non decreasing etc. TimestampType doesn't have those semantics enforced, it > just knows what to do with given 64 bits. Therefore, I removed the timestamp > type field in the HTableDescriptor. > Open for suggestions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16210) Add Timestamp class to the hbase-common
[ https://issues.apache.org/jira/browse/HBASE-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16210: Status: Patch Available (was: Open) > Add Timestamp class to the hbase-common > --- > > Key: HBASE-16210 > URL: https://issues.apache.org/jira/browse/HBASE-16210 > Project: HBase > Issue Type: Sub-task >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: patch, testing > Attachments: HBASE-16210.master.1.patch, HBASE-16210.master.2.patch, > HBASE-16210.master.3.patch, HBASE-16210.master.4.patch, > HBASE-16210.master.5.patch, HBASE-16210.master.6.patch, > HBASE-16210.master.7.patch, HBASE-16210.master.8.1.patch, > HBASE-16210.master.8.2.patch, HBASE-16210.master.8.3.patch, > HBASE-16210.master.8.4.patch, HBASE-16210.master.8.patch > > > This is a sub-issue of > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070]. This JIRA is > a small step towards completely adding Hybrid Logical Clocks(HLC) to HBase. > The main idea of HLC is described in > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070] along with > the motivation of adding it to HBase. > This patch in this issue takes the code from the patch in the parent. > The parent patch is pretty big to review at once. So, plan is to get code > reviewed in smaller patches and > in the process take suggestions and change things if necessary. > What is this patch/issue about ? > This issue attempts to add a timestamp class to hbase-common and timestamp > type to HTable. > This is a part of the attempt to get HLC into HBase. This patch does not > interfere with the current working of HBase. > Why Timestamp Class ? > Timestamp class can be as an abstraction to represent time in Hbase in 64 > bits. > It is just used for manipulating with the 64 bits of the timestamp and is not > concerned about the actual time. > There are three types of timestamps. System time, Custom and HLC. Each one of > it has methods to manipulate the 64 bits of timestamp. > HTable changes: Added a timestamp type property to HTable. This will help > HBase exist in conjunction with old type of timestamp and also the HLC which > will be introduced. The default is set to custom timestamp(current way of > usage of timestamp). default unset timestamp is also custom timestamp as it > should be so. The default timestamp will be changed to HLC when HLC feature > is introduced completely in HBase. > Check HBASE-16210.master.6.patch. > Update: Based on the suggestions, made timestamp enum. Here is the > description of the new changes. > Check the HBASE-16210.master.8.1.patch > 1. Changed the Timestamp Implementation to Enum. > 2. Changed the Timestamp semantics. Instead of HLC, System monotonic and > custom, we now have Hybrid and Physical. System monotonic clock and Custom > clocks can map their timestamps to Physical. HLC clock can map its timestamp > to Hybrid. > 3. The HTableDescriptor will contain clock type(not implemented yet) instead > of timestamp type. As clocks convey the semantics of monotonic increasing and > non decreasing etc. TimestampType doesn't have those semantics enforced, it > just knows what to do with given 64 bits. Therefore, I removed the timestamp > type field in the HTableDescriptor. > Open for suggestions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16210) Add Timestamp class to the hbase-common
[ https://issues.apache.org/jira/browse/HBASE-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16210: Attachment: (was: HBASE-16210.master.8.4.patch) > Add Timestamp class to the hbase-common > --- > > Key: HBASE-16210 > URL: https://issues.apache.org/jira/browse/HBASE-16210 > Project: HBase > Issue Type: Sub-task >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: patch, testing > Attachments: HBASE-16210.master.1.patch, HBASE-16210.master.2.patch, > HBASE-16210.master.3.patch, HBASE-16210.master.4.patch, > HBASE-16210.master.5.patch, HBASE-16210.master.6.patch, > HBASE-16210.master.7.patch, HBASE-16210.master.8.1.patch, > HBASE-16210.master.8.2.patch, HBASE-16210.master.8.3.patch, > HBASE-16210.master.8.patch > > > This is a sub-issue of > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070]. This JIRA is > a small step towards completely adding Hybrid Logical Clocks(HLC) to HBase. > The main idea of HLC is described in > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070] along with > the motivation of adding it to HBase. > This patch in this issue takes the code from the patch in the parent. > The parent patch is pretty big to review at once. So, plan is to get code > reviewed in smaller patches and > in the process take suggestions and change things if necessary. > What is this patch/issue about ? > This issue attempts to add a timestamp class to hbase-common and timestamp > type to HTable. > This is a part of the attempt to get HLC into HBase. This patch does not > interfere with the current working of HBase. > Why Timestamp Class ? > Timestamp class can be as an abstraction to represent time in Hbase in 64 > bits. > It is just used for manipulating with the 64 bits of the timestamp and is not > concerned about the actual time. > There are three types of timestamps. System time, Custom and HLC. Each one of > it has methods to manipulate the 64 bits of timestamp. > HTable changes: Added a timestamp type property to HTable. This will help > HBase exist in conjunction with old type of timestamp and also the HLC which > will be introduced. The default is set to custom timestamp(current way of > usage of timestamp). default unset timestamp is also custom timestamp as it > should be so. The default timestamp will be changed to HLC when HLC feature > is introduced completely in HBase. > Check HBASE-16210.master.6.patch. > Update: Based on the suggestions, made timestamp enum. Here is the > description of the new changes. > Check the HBASE-16210.master.8.1.patch > 1. Changed the Timestamp Implementation to Enum. > 2. Changed the Timestamp semantics. Instead of HLC, System monotonic and > custom, we now have Hybrid and Physical. System monotonic clock and Custom > clocks can map their timestamps to Physical. HLC clock can map its timestamp > to Hybrid. > 3. The HTableDescriptor will contain clock type(not implemented yet) instead > of timestamp type. As clocks convey the semantics of monotonic increasing and > non decreasing etc. TimestampType doesn't have those semantics enforced, it > just knows what to do with given 64 bits. Therefore, I removed the timestamp > type field in the HTableDescriptor. > Open for suggestions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16210) Add Timestamp class to the hbase-common
[ https://issues.apache.org/jira/browse/HBASE-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Teja Ranuva updated HBASE-16210: Attachment: HBASE-16210.master.8.4.patch > Add Timestamp class to the hbase-common > --- > > Key: HBASE-16210 > URL: https://issues.apache.org/jira/browse/HBASE-16210 > Project: HBase > Issue Type: Sub-task >Reporter: Sai Teja Ranuva >Assignee: Sai Teja Ranuva >Priority: Minor > Labels: patch, testing > Attachments: HBASE-16210.master.1.patch, HBASE-16210.master.2.patch, > HBASE-16210.master.3.patch, HBASE-16210.master.4.patch, > HBASE-16210.master.5.patch, HBASE-16210.master.6.patch, > HBASE-16210.master.7.patch, HBASE-16210.master.8.1.patch, > HBASE-16210.master.8.2.patch, HBASE-16210.master.8.3.patch, > HBASE-16210.master.8.patch > > > This is a sub-issue of > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070]. This JIRA is > a small step towards completely adding Hybrid Logical Clocks(HLC) to HBase. > The main idea of HLC is described in > [HBase-14070|https://issues.apache.org/jira/browse/HBASE-14070] along with > the motivation of adding it to HBase. > This patch in this issue takes the code from the patch in the parent. > The parent patch is pretty big to review at once. So, plan is to get code > reviewed in smaller patches and > in the process take suggestions and change things if necessary. > What is this patch/issue about ? > This issue attempts to add a timestamp class to hbase-common and timestamp > type to HTable. > This is a part of the attempt to get HLC into HBase. This patch does not > interfere with the current working of HBase. > Why Timestamp Class ? > Timestamp class can be as an abstraction to represent time in Hbase in 64 > bits. > It is just used for manipulating with the 64 bits of the timestamp and is not > concerned about the actual time. > There are three types of timestamps. System time, Custom and HLC. Each one of > it has methods to manipulate the 64 bits of timestamp. > HTable changes: Added a timestamp type property to HTable. This will help > HBase exist in conjunction with old type of timestamp and also the HLC which > will be introduced. The default is set to custom timestamp(current way of > usage of timestamp). default unset timestamp is also custom timestamp as it > should be so. The default timestamp will be changed to HLC when HLC feature > is introduced completely in HBase. > Check HBASE-16210.master.6.patch. > Update: Based on the suggestions, made timestamp enum. Here is the > description of the new changes. > Check the HBASE-16210.master.8.1.patch > 1. Changed the Timestamp Implementation to Enum. > 2. Changed the Timestamp semantics. Instead of HLC, System monotonic and > custom, we now have Hybrid and Physical. System monotonic clock and Custom > clocks can map their timestamps to Physical. HLC clock can map its timestamp > to Hybrid. > 3. The HTableDescriptor will contain clock type(not implemented yet) instead > of timestamp type. As clocks convey the semantics of monotonic increasing and > non decreasing etc. TimestampType doesn't have those semantics enforced, it > just knows what to do with given 64 bits. Therefore, I removed the timestamp > type field in the HTableDescriptor. > Open for suggestions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
