Cloudera Labs
Provide feedback on Cloudera Labs
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

CDH Supported Phoenix

SOLVED Go to solution

Re: CDH Supported Phoenix

Cloudera Employee

The current CLabs phoenix that works against C5.5 will likely fail. We are in the process of creating a new Cloudera Labs version of Phoenix that is compatible with the C5.7 line.  

 

Jon.

Jonathan Hsieh (shay)
Software Engineer, Cloudera

Re: CDH Supported Phoenix

New Contributor
Thank you.

Re: CDH Supported Phoenix

New Contributor

Any idea when will this new Phoenix version be available for CDH 5.7?

Re: CDH Supported Phoenix

Expert Contributor

Cloudera Labs is a way for us to gauge community interest in new and promising projects. It is not a guarantee of future commercial support by Cloudera but some projects have in the past have become commercially supported or integrated into supported upstream projects.

 

 

Could you share repo with phoenix built for CDH? So community could take part in it. 

Re: CDH Supported Phoenix

Master Collaborator
Highlighted

Re: CDH Supported Phoenix

Explorer

I am trying to run Phoenix 4.5.2 on CDH 5.7. I successfully installed it thorough parcels, but I am having issue starting it. 

It is giving me this error:

 

Error: SYSTEM.CATALOG (state=08000,code=101)
org.apache.phoenix.exception.PhoenixIOException: SYSTEM.CATALOG
at org.apache.phoenix.util.ServerUtil.parseServerException(ServerUtil.java:108)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:1051)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:1014)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(ConnectionQueryServicesImpl.java:1259)
at org.apache.phoenix.query.DelegateConnectionQueryServices.createTable(DelegateConnectionQueryServices.java:113)
at org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClient.java:1937)
at org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:751)
at org.apache.phoenix.compile.CreateTableCompiler$2.execute(CreateTableCompiler.java:186)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:320)
at org.apache.phoenix.jdbc.PhoenixStatement$2.call(PhoenixStatement.java:312)
at org.apache.phoenix.call.CallRunner.run(CallRunner.java:53)
at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:310)
at org.apache.phoenix.jdbc.PhoenixStatement.executeUpdate(PhoenixStatement.java:1422)
at org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:1927)
at org.apache.phoenix.query.ConnectionQueryServicesImpl$12.call(ConnectionQueryServicesImpl.java:1896)
at org.apache.phoenix.util.PhoenixContextExecutor.call(PhoenixContextExecutor.java:77)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQueryServicesImpl.java:1896)
at org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixDriver.java:180)
at org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.connect(PhoenixEmbeddedDriver.java:132)
at org.apache.phoenix.jdbc.PhoenixDriver.connect(PhoenixDriver.java:151)
at sqlline.DatabaseConnection.connect(DatabaseConnection.java:157)
at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:203)
at sqlline.Commands.connect(Commands.java:1064)
at sqlline.Commands.connect(Commands.java:996)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:36)
at sqlline.SqlLine.dispatch(SqlLine.java:804)
at sqlline.SqlLine.initArgs(SqlLine.java:588)
at sqlline.SqlLine.begin(SqlLine.java:656)
at sqlline.SqlLine.start(SqlLine.java:398)
at sqlline.SqlLine.main(SqlLine.java:292)
Caused by: org.apache.hadoop.hbase.TableNotFoundException: SYSTEM.CATALOG
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(ConnectionManager.java:1297)
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1125)
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1109)
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1066)
at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.getRegionLocation(ConnectionManager.java:901)
at org.apache.hadoop.hbase.client.HTable.getRegionLocation(HTable.java:558)
at org.apache.hadoop.hbase.client.HTable.getKeysAndRegionsInRange(HTable.java:817)
at org.apache.hadoop.hbase.client.HTable.getKeysAndRegionsInRange(HTable.java:787)
at org.apache.hadoop.hbase.client.HTable.getStartKeysInRange(HTable.java:1830)
at org.apache.hadoop.hbase.client.HTable.coprocessorService(HTable.java:1785)
at org.apache.hadoop.hbase.client.HTable.coprocessorService(HTable.java:1765)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.metaDataCoprocessorExec(ConnectionQueryServicesImpl.java:1034)
... 32 more

 

Please let me knwo if any of you have any suggestions. It says 'SYSTEM.CATALOG' table not found. I checked and the table exists in path /hbase/data/default/SYSTEM.CATALOG' but path for hbase root dir is different and there is no SYSTEM tables on that path. I tried changing the hbase root dir path to the path wehre CATALOG table exists but no luck with that either.

Re: CDH Supported Phoenix

Master Collaborator

uzi,

 

The Phoenix 4.5.2 parcel is not designed for/was not tested on CDH 5.7, so no surprise. A new parcel for 5.7 is under consideration.

Re: CDH Supported Phoenix

Explorer

Thnak You for your quick reply.

 

We are running Phoenix 4.5.2 on CDH 5.6, and it is running fine (apart from some connection issue when combining phoenix with spark application). I want to run phoenix on CDH 5.7 as well, do you have any suggestions on how I can make this happen, or what version of phoenix will suit better. I am aware that these things are still on research phase, but I also do not want to downgrade 5.7 to 5.6 to have phoenix.

Re: CDH Supported Phoenix

Master Collaborator

I think you'll see a new parcel for 5.7 pretty soon. Please stand by...

Re: CDH Supported Phoenix

Expert Contributor