[HBASE-15484] Correct the semantic of batch and partial

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.4.0, 2.0.0
• Fix Version/s: 1.4.0, 2.0.0
• Component/s: Client, Scanners
• Hadoop Flags: Reviewed

Release Note

Now setBatch doesn't mean setAllowPartialResult(true)
If user setBatch(5) and rpc returns 3+5+5+5+3 cells, we should return 5+5+5+5+1 to user.
Scan#setBatch is helpful in paging queries, if you just want to prevent OOM at client, use setAllowPartialResults(true) is better.
We deprecated isPartial and use mayHaveMoreCellsInRow. If it returns false, current Result must be the last one of this row.

• Assignee: Phil Yang
• Reporter: Phil Yang
• Created: 18/Mar/16 11:20
• Updated: 07/May/19 16:11
• Resolved: 07/Mar/17 15:05

Description

Follow-up to HBASE-15325, as discussed, the meaning of setBatch and setAllowPartialResults should not be same. We should not regard setBatch as setAllowPartialResults.

Now we deprecated isPartial and use mayHaveMoreCellsInRow. If it returns false, current Result must be the last one of this row.

Issue Links

• relates to: HBASE-17740 Correct the semantic of batch and partial for async client
• relates to: HBASE-15325 ResultScanner allowing partial result will miss the rest of the row if the region is moved between two rpc requests
• relates to: HBASE-11544 [Ergonomics] hbase.client.scanner.caching is dogged and will try to return batch even if it means OOME
• links to: Review board