Can you just add static logging to Filter? Especially around
construction and in the read/write methods used serializing? Hopefully
will turn up a clue as to whats going on.
St.Ack
Przemek wrote:
stack wrote:
One thought: your new class is on the CLASSPATH on both sides of the
communication -- server and client?
St.Ack
yes. I also created my own test extending HBaseClusterTestCase to have
everything in one process and the behaviour was similar - call to
write() and then scanning, many logs on the console, write(), scanning,
again and again endlessly.
BTW, is there any test case for testing custom filter in action (that is
passed to getScanner method) ? Couln't find any.
Przemek
