could you double check your hbase's classpath? we've got the same problem over here and, in our case, some third-party jars needed by our custom filter implementation were missing. Maybe this is happening with you too.
On Mon, Mar 15, 2010 at 3:29 PM, Slava Gorelik <slava.gore...@gmail.com>wrote: > Hi. > Thank You for your reply. > I'm using 0.20.3 on server and client. > I looked in the mailing list and saw couple of messages with the same > problem, but > didn't get any idea how to fix the problem. > My scanner is less than alive 1 minute (less then 10 seconds) , i use > 0.20.3 > on server and the client. > > Thank You and Best Regards. > > > On Mon, Mar 15, 2010 at 8:08 PM, Jean-Daniel Cryans <jdcry...@apache.org > >wrote: > > > If you search the mailing list, you'll see the same issue came up > > recently. Make sure you don't have clients running on 0.20.1 > > > > J-D > > > > On Mon, Mar 15, 2010 at 10:15 AM, Slava Gorelik <slava.gore...@gmail.com > > > > wrote: > > > Hi. > > > I'm trying to create a scanner with custom (Hbase 0.20.3) filter and > it > > > looks like RegionServer throws an exception: > > > org.apache.hadoop.hbase.UnknownScannerException: Name: -1 > > > > > > I have my custom filters compiled as a jar and placed in the CLASSPATH > in > > > the RegionServer. > > > What could be a problem ? > > > > > > Thank You and Best Regards. > > > > > > -- Guilherme msn: guigermog...@hotmail.com homepage: http://sites.google.com/site/germoglio/
