You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2018/06/06 20:02:00 UTC

[jira] [Created] (HBASE-20692) Help Phoenix better identify itself when something goes wrong on a cluster

Sean Busbey created HBASE-20692:
-----------------------------------

             Summary: Help Phoenix better identify itself when something goes wrong on a cluster
                 Key: HBASE-20692
                 URL: https://issues.apache.org/jira/browse/HBASE-20692
             Project: HBase
          Issue Type: Wish
          Components: community
    Affects Versions: 2.0.0
            Reporter: Sean Busbey


User list question about a failing 2.0.0 test cluster came in[1], turned out to be Phoenix installed but missing from the classpath. Problem area wasn't immediately obvious because the ClassNotFoundException appeared to be for an HBase class: org.apache.hadoop.hbase.regionserver.wal.IndexedWALEditCodec.

Checking on recent-ish phoenix, they have a bunch of classes in org.apache.hadoop.hbase[2]. Presumably to circumvent package-protected access restrictions, but I didn't check.

Should come up with some ways to make it more obvious when our shared users need to talk with them. this jira's a place to collect some suggestions once folks have a chance to see why phoenix is in our package space in the first place. Once we have something concrete to propose we can take the suggestions over to dev@phoenix.

[1]: https://s.apache.org/oqfr

[2]: https://github.com/apache/phoenix/tree/v5.0.0-alpha-HBase-2.0/phoenix-core/src/main/java/org/apache/hadoop/hbase



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)