Adam,
One thought... the phoenix client jar is a shaded jar which I think
bundles hbase-common so maybe the end result was two versions of
ClassSize being on the classpath and it not being clear which one was
being used.
Also, a NoClassDefFoundError can be thrown if some static code in the
class
Bryan,
Yes, an HBase client upgrade makes sense for the Java 10 upgrade path. However,
the NoClassDefFoundError is more mysterious and does concern me.
Thanks,
Adam
On 8/23/18, 12:12 PM, "Bryan Bende" wrote:
Adam,
Yes for now Java 8 is what is fully supported.
Bryan,
We are running HBase 1.2. I am confused as well about the missing ClassSize
class. Does seem completely unrelated to Pheonix and I do not understand why
adding the client would help resolve the class.
Would you advise reverting to Java 8 until Java 10 is fully supported?
Thanks,
Adam,
Yes for now Java 8 is what is fully supported.
Hopefully the remaining issues can be resolved in the not too distant
future to become compatible with Java 9+.
I know in the HBase case it requires changing to a newer version of
the client because the 1.1.2 client has the code that caused
Adam,
The ClassSize class comes from hbase-common [1] so I'm not sure how
that would related to the Phoenix client JAR. What version of HBase
was this against?
The only case I know of that needs the Phoenix client jar is when
Phoenix has been installed which then modifies the HBase config files
