[HBASE-16593] Unify HTable with AP

• Type: Umbrella
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Heng Chen
• Reporter: Heng Chen
• Created: 09/Sep/16 09:45
• Updated: 27/Oct/16 16:17

Description

Currently, HTable has two ways to deal with request, one is call RPC directly, it is used to processed single action request such as Get, Delete, Append, Increment. Another one is through AP to deal with multi action requests, such as batch, mutation etc.

This issue is to unify them with AP only. It has some benefits, for example we could implements async interface easily with AP, and we could make the client logic more clear just use AP to communicate with Server.

HBASE-14703 has done some work (unify mutate and checkAndMutate with AP)

Issue Links

• is related to: HBASE-14703 HTable.mutateRow does not collect stats
• is related to: HBASE-16575 unify the semantic of RRCI#callWithRetries and RRCI#callWithoutRetries when the maxAttempts is configured to one

Sub-Tasks

• Reduce redundant interfaces in AsyncProcess: Resolved
• Revisit the threadPool is really needed in submitAll and submit interface in AsyncProcess: Resolved
• Remove some duplicate code in HTable: Resolved
• Make NoncedRegionServerCallable extend CancellableRegionServerCallable: Resolved
• Unify Delete request with AP: Resolved
• Performance test for interface unified with AP: Open
• Unify append, increment with AP: Patch Available
• Unify Get with AP: Open
• Extract AsyncRequestFuture related code from AsyncProcess: Resolved
• Figure out performance difference between increment and append: Open
• Unify HTable#checkAndDelete with AP: Resolved
• Unify HTable#checkAndPut with AP: Resolved