On Sun, Sep 8, 2013 at 4:19 AM, Amit Sela <[email protected]> wrote:
> I did some debug and I have more input about my issue. The Configuration in > Compression.Algorithm has a class loader that holds reference to the > original package (loaded at restart) and not to e current one (loaded after > package update). Is the compression algorithm cached somewhere such that > after a first time read (get, scan) from hbase, the following uses use a > cached instance ? Yes. Does this rather than reload each time. Let me know if you need more help getting this all up and running. Am interested in your findings. St.Ack
