hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "HBase Review Board (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2002) Coprocessors: Client side support
Date Tue, 05 Oct 2010 21:47:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918234#action_12918234

HBase Review Board commented on HBASE-2002:

Message from: "Andrew Purtell" <apurtell@apache.org>

This is an automatically generated e-mail. To reply, visit:


    Could be setCause


    Agree, subpackage would be a pain but Javadoc can make it explicit for sure.


    Only one instance of a given Coprocessor class can be bound to a region at a time.


    This is pretty generic but currently has no other use, correct.


    We should be getting rid of RowRange, right?


    Good, likewise for exec() as below.

- Andrew

> Coprocessors: Client side support
> ---------------------------------
>                 Key: HBASE-2002
>                 URL: https://issues.apache.org/jira/browse/HBASE-2002
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Gary Helmling
>             Fix For: 0.90.0
> "High-level call interface for clients. Unlike RPC, calls addressed to rows or ranges
of rows. Coprocessor client library resolves to actual locations. Calls across multiple rows
automatically split into multiple parallelized RPCs"
> Generic multicall RPC facility which incorporates this and multiget/multiput/multidelete
and parallel scanners.
> Group and batch RPCs by region server. Track and retry outstanding RPCs. Ride over region
> Support addressing by explicit region identifier or by row key or row key range. 
> Include a facility for merging results client side. 

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

View raw message