[jira] [Updated] (HBASE-12510) Remove the dependency on 0.89-fb branch for HydraBase
[ https://issues.apache.org/jira/browse/HBASE-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Menghani updated HBASE-12510: Attachment: 0002-HBASE-12510-Make-hbase-consensus-independent-of-HReg.patch Attached second patch after addressing Ted's comments. Remove the dependency on 0.89-fb branch for HydraBase - Key: HBASE-12510 URL: https://issues.apache.org/jira/browse/HBASE-12510 Project: HBase Issue Type: Sub-task Components: wal Reporter: Rishit Shroff Assignee: Gaurav Menghani Priority: Minor Attachments: 0001-HBASE-12510-Make-hbase-consensus-independent-of-HReg.patch, 0002-HBASE-12510-Make-hbase-consensus-independent-of-HReg.patch The current RAFT protocol implementation depends on few classes (8) which were present in 0.89-fb branch. The latest HBase branch may have other equivalents of it and we need to cleanup/refactor to code to use them. Filing this JIRA to track this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12510) Remove the dependency on 0.89-fb branch for HydraBase
[ https://issues.apache.org/jira/browse/HBASE-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Menghani updated HBASE-12510: Attachment: 0001-HBASE-12510-Make-hbase-consensus-independent-of-HReg.patch Everyone seems okay with this first patch. We still need to do more work on this JIRA to completely remove 0.89-fb dependencies. This one would get us unblocked w.r.t work being done in other JIRAs. Remove the dependency on 0.89-fb branch for HydraBase - Key: HBASE-12510 URL: https://issues.apache.org/jira/browse/HBASE-12510 Project: HBase Issue Type: Sub-task Components: wal Reporter: Rishit Shroff Assignee: Gaurav Menghani Priority: Minor Attachments: 0001-HBASE-12510-Make-hbase-consensus-independent-of-HReg.patch The current RAFT protocol implementation depends on few classes (8) which were present in 0.89-fb branch. The latest HBase branch may have other equivalents of it and we need to cleanup/refactor to code to use them. Filing this JIRA to track this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
