hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2611) [hbase] Create a RowMutation class in the public API
Date Mon, 28 Jan 2008 21:01:34 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563281#action_12563281
] 

Bryan Duxbury commented on HADOOP-2611:
---------------------------------------

I will incorporate suggestions into a new patch.

The rationale behind using a new class for the public API was that we didn't necessarily want
to expose the BatchUpdate because it's part of our server protocol. I wouldn't be against
making server take RowMutations or exposing BatchUpdate if that makes more sense in the long
run. I was also trying to remove the worthless update code and such needing to be created.

> [hbase] Create a RowMutation class in the public API
> ----------------------------------------------------
>
>                 Key: HADOOP-2611
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2611
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: contrib/hbase
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Minor
>         Attachments: 2611.patch
>
>
> Today, when you want to interact with a row in HBase, you start an update, make changes,
and then commit the lock. This is fine for very simple applications. However, when you try
to do things like support table operations as part of a MapReduce job, it becomes more difficult
to support.
> I propose that we create a new class, RowMutation (a la the Bigtable paper), which encapsulates
a group of actions on a row, and make this available to API consumers. It might look something
like:
> {code}
> RowMutation r = table.getMutation(row_key);
> r.setTimestamp(1111);
> r.put(new Text("colfam1:name", value));
> r.delete(new Text("colfam2:deleted"));
> table.commit(r);
> {code}
> This syntax would supercede the existing startUpdate/commit format, which could be deprecated
and mapped to a RowMutation behind the scenes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message