Hi,
When I experimented with HBASE-1512, I got the following from
HbaseObjectWritable:
java.lang.UnsupportedOperationException: No code for unexpected class
org.apache.hadoop.hbase.client.coprocessor.AggregationClient$1LongColumnInterpreter

I think there was initiative to support dynamic class registration in
HbaseObjectWritable

If someone can enlighten me on the above, that would be great.

Hi Ted,

First, just to make sure, LongColumnInterpreter implements either Writable
or Serializable, right?

If so (I assume this is based on current trunk), sounds like a bug to me.
There have been a couple changes over the past several months to allow
HbaseObjectWritable to serialize Writables with no code by classname and to
also support Serializable as a fall back.

--gh
On Thu, Mar 31, 2011 at 9: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
>
> org.apache.hadoop.hbase.client.coprocessor.AggregationClient$1LongColumnInterpreter
>
> I think there was initiative to support dynamic class registration in
> HbaseObjectWritable
>
> If someone can enlighten me on the above, that would be great.
>

Gary:
Thanks for responding.
I switched to using Serializable instead of Writable because currently the
interpreter is stateless.

Please take a look at LongColumnInterpreter inside this file:
https://issues.apache.org/jira/secure/attachment/12475130/AggregationClient.java

On Thu, Mar 31, 2011 at 10:16 AM, Gary Helmling <[EMAIL PROTECTED]> wrote:

> Hi Ted,
>
> First, just to make sure, LongColumnInterpreter implements either Writable
> or Serializable, right?
>
> If so (I assume this is based on current trunk), sounds like a bug to me.
> There have been a couple changes over the past several months to allow
> HbaseObjectWritable to serialize Writables with no code by classname and to
> also support Serializable as a fall back.
>
> --gh
>
>
> On Thu, Mar 31, 2011 at 9: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
> >
> >
> org.apache.hadoop.hbase.client.coprocessor.AggregationClient$1LongColumnInterpreter
> >
> > I think there was initiative to support dynamic class registration in
> > HbaseObjectWritable
> >
> > If someone can enlighten me on the above, that would be great.
> >
>

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.

Himanshu

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
>
> org.apache.hadoop.hbase.client.coprocessor.AggregationClient$1LongColumnInterpreter
>
> I think there was initiative to support dynamic class registration in
> HbaseObjectWritable
>
> If someone can enlighten me on the above, that would be great.
>