[ https://issues.apache.org/jira/browse/PHOENIX-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610703#comment-14610703 ]
Mujtaba Chohan commented on PHOENIX-2025: ----------------------------------------- IndexToolIT are still fails for 0.98/1.0 after setting hbase.defaults.for.version.skip to true. https://builds.apache.org/view/H-L/view/Phoenix/job/Phoenix-4.x-HBase-0.98/752/console https://builds.apache.org/view/H-L/view/Phoenix/job/Phoenix-4.x-HBase-1.0/77/console > Phoenix-core's hbase-default.xml prevents HBaseTestingUtility from starting > up in client apps > --------------------------------------------------------------------------------------------- > > Key: PHOENIX-2025 > URL: https://issues.apache.org/jira/browse/PHOENIX-2025 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.3.0 > Reporter: Geoffrey Jacoby > Assignee: Geoffrey Jacoby > Fix For: 5.0.0, 4.5.0, 4.4.1 > > Attachments: PHOENIX-2025.patch, PHOENIX-2025_v2.patch > > > Phoenix seems to have long had its own version of hbase-default.xml as a test > resource in phoenix-core with a single setting to override > hbase.defaults.for.version.skip to true. Sometime around Phoenix 4.3, > phoenix-core seems to have been split into a main jar and a test jar, and the > hbase-default.xml went into the test jar. > The odd result of this is that in client apps that include the test jar, the > classloader in HBaseConfiguration.create() now sees Phoenix's > hbase-default.xml, rather than HBase's, and creates a Configuration object > without HBase's defaults. One major consequence of this is that the > HBaseTestingUtility can't start up, because it relies on those HBase defaults > being set. This is a huge problem in a client app that includes the > phoenix-core test jar in order to make use of the PhoenixTestDriver and > BaseTest classes; the upgrade to 4.3 breaks all tests using the > HBaseTestingUtility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)