[HBASE-2609] Harmonize the Get and Delete operations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.99.2
• Component/s: Client
• Hadoop Flags: Reviewed
• Release Note: Align Delete class with Get class. Change all delete* method names to add* instead. For example, change deleteColumn to addColumn (as in add-this-column to the Delete specification). Deprecate the old.
• Assignee: Michael Stack
• Reporter: Jeff Hammerbacher
• Created: 24/May/10 10:34
• Updated: 06/Apr/18 17:55
• Resolved: 26/Oct/14 03:59

Description

In my work on HBASE-2400, implementing deletes for the Avro server felt quite awkward. Rather than the clean API of the Get object, which allows restrictions on the result set from a row to be expressed with addColumn, addFamily, setTimeStamp, setTimeRange, setMaxVersions, and setFilters, the Delete object hides these semantics behind various constructors to deleteColumn[s] an deleteFamily. From my naive vantage point, I see no reason why it would be a bad idea to mimic the Get API exactly, though I could quite possibly be missing something. Thoughts?

Issue Links

• is related to: HBASE-2051 Use builder pattern to improve usability of client API
• relates to: HBASE-2648 API Rework: Have Delete and Put implement same Interface or subclass same 'Mutation' ancestor (Get too? And Result?)
• relates to: HBASE-2930 API Put takes List but Delete takes ArrayList - seems inconsistent
• relates to: HBASE-10856 Prep for 1.0