[HBASE-1249] Rearchitecting of server, client, API, key format, etc for 0.20

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Invalid
• Fix Version/s: 0.20.0
• Assignee: Jonathan Gray
• Reporter: Jonathan Gray
• Created: 09/Mar/09 17:32
• Updated: 20/Sep/18 18:37
• Resolved: 26/May/09 15:55

Description

To discuss all the new and potential issues coming out of the change in key format (HBASE-1234): zero-copy reads, client binary protocol, update of API (HBASE-880), server optimizations, etc...

Issue Links

• blocks: HBASE-1212 merge tool expects regions all have different sequence ids
• blocks: HBASE-1015 HBase Native Client Library
• blocks: HBASE-1304 New client server implementation of how gets and puts are handled.
• incorporates: HBASE-861 get with timestamp will return a value if there is a version with an earlier timestamp
• incorporates: HBASE-899 Support for specifying a timestamp and numVersions on a per-column basis
• incorporates: HBASE-52 [hbase] Add a means of scanning over all versions
• incorporates: HBASE-1014 commit(BatchUpdate) method should return timestamp
• relates to: HBASE-867 If millions of columns in a column family, hbase scanner won't come up
• relates to: HBASE-1206 Scanner spins when there are concurrent inserts to column family
• relates to: HBASE-61 [hbase] Create an HBase-specific MapFile implementation
• relates to: HBASE-1234 Change HBase StoreKey format