hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3811) Allow adding attributes to Scan
Date Wed, 27 Apr 2011 00:01:08 GMT

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

stack commented on HBASE-3811:
------------------------------

You could change Scan so it passes an optional Map.   Add an attributes method to Scan.  If
attributes > 0, instantiate a Map and then serialize it out.  On other end, have check
for null or non-null Map when deserializing (We don't want to carry the Map for every Scan
I'd say -- just carry it when attributes present... but perhaps I'm doing premature optimization
here).

This could become more important now we have CPs.

> Allow adding attributes to Scan
> -------------------------------
>
>                 Key: HBASE-3811
>                 URL: https://issues.apache.org/jira/browse/HBASE-3811
>             Project: HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Alex Baranau
>            Priority: Minor
>
> There's sometimes a need to add custom attribute to Scan object so that it can be accessed
on server side.
> Example of the case where it is needed discussed here: http://search-hadoop.com/m/v3Jtb2GkiO.
There might be other cases where it is useful, which are mostly about logging/gathering stats
on server side.
> Alternative to allowing adding any custom attributes to scan could be adding some fixed
field, like "type" to the class.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message