-Re: ColumnInterpreter and HbaseObjectWritable Was: HbaseObjectWritable and UnsupportedOperationException
Himanshu Vashishtha 2011-04-01, 06:59
Really! I think it doesn't make any difference as Long class is already
loaded (used by number of classes like HRInfo, HConstants, HFile etc). And
since these are static final fields (part of the class description in method
area). It should be there much before this Coprocessor loading. I am still
learning this stuff, will be great to hear your/other opinion.
On Thu, Mar 31, 2011 at 10:18 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
> I found the one more benefit of using (enhanced) interpreter.
> We load AggregateProtocolImpl.class into CoprocessorHost. Interpreter feeds
> various values (such as Long.MIN_VALUE) of concrete type (Long) into
> AggregateProtocolImpl. This simplifies class loading for CoprocessorHost
> On Thu, Mar 31, 2011 at 11:37 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
>> Renaming the subject to better reflect the nature of further discussion.
>> There're two considerations for my current implementation attached to
>> 1. User shouldn't modify HbaseObjectWritable directly for the new class
>> which is to be executed on region server.
>> 2. The reason for introducing interpreter is that we (plan to) store
>> objects of MeasureWritable, a relatively complex class, in hbase. Using
>> interpreter would give us flexibility in computing aggregates.
>> On Thu, Mar 31, 2011 at 10:01 AM, Himanshu Vashishtha <
>> [EMAIL PROTECTED]> wrote:
>>> Hello Ted,
>>> Did you add a new class: LongColumnInterpreter. Is this the new argument
>>> type you want to define to pass along rpcs. For all such "new" argument
>>> types, they should be supported/backed up with in the HbaseObjectWritable
>>> class to read/write it on wire. Do we really need it, just wondering.
>>> On Thu, Mar 31, 2011 at 10:52 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>> > Hi,
>>> > When I experimented with HBASE-1512, I got the following from
>>> > HbaseObjectWritable:
>>> > java.lang.UnsupportedOperationException: No code for unexpected class
>>> > I think there was initiative to support dynamic class registration in
>>> > HbaseObjectWritable
>>> > If someone can enlighten me on the above, that would be great.