[
https://issues.apache.org/jira/browse/HBASE-15484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Yang updated HBASE-15484:
------------------------------
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.
was:
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.
We deprecated isPartial and use mayHaveMoreCellsInRow. If it returns false,
current Result must be the last one of this row.
> Correct the semantic of batch and partial
> -----------------------------------------
>
> Key: HBASE-15484
> URL: https://issues.apache.org/jira/browse/HBASE-15484
> Project: HBase
> Issue Type: Sub-task
> Components: Client, scan
> Affects Versions: 2.0.0, 1.4.0
> Reporter: Phil Yang
> Assignee: Phil Yang
> Priority: Blocker
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-15484.amend.patch, HBASE-15484.branch-1.v01.patch,
> HBASE-15484.v05.patch, HBASE-15484.v06.patch, HBASE-15484-v1.patch,
> HBASE-15484-v2.patch, HBASE-15484-v3.patch, HBASE-15484-v4.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
