[
https://issues.apache.org/jira/browse/HBASE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669131#action_12669131
]
Andrew Purtell commented on HBASE-880:
--------------------------------------
Hi Erik,
I think there are two issues with your use case, right? The first is you need
some filters that do not currently exist that provide the topmost column
filtering behavior that you want. The second issue is the modification to
getRow() so it behaves kind of like a column scanner. If there are suitable
filters available would it would be possible to use the scanner interface with
a combination filter such as:
{code}
(and
(allow-n-rows 1)
(and
(match-column "foo:")
(allow-n-columns 100)
)
)
{code}
to do what you want?
> Improve the current client API by creating new container classes
> ----------------------------------------------------------------
>
> Key: HBASE-880
> URL: https://issues.apache.org/jira/browse/HBASE-880
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: client
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.20.0
>
> Attachments: 880.patch, 880proposal4plus-v2.patch,
> 880proposal4plus.patch, 880proposal5-v2.patch, 880proposal5-v2.png,
> 880proposal5.patch, 880proposal5.png, hbase-880-patch.jpg,
> hbase-880-proposal4.patch, hbase-880-v1.patch, hbase-880-v2.patch,
> hbase_client_classes.png, NewCilentAPIProposoal4.gif, proposal2.jpg,
> proposed.jpg
>
> Original Estimate: 240h
> Remaining Estimate: 240h
>
> The current API does not scale very well. For each new feature, we have to
> add many methods to take care of all the overloads. Also, the need to batch
> row operations (gets, inserts, deletes) implies that we have to manage some
> "entities" like we are able to do with BatchUpdate but not with the other
> operations. The RowLock should be an attribute of such an entity.
> The scope of this jira is only to replace current API with another
> feature-compatible one, other methods will be added in other issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
