[ 
https://issues.apache.org/jira/browse/PHOENIX-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995213#comment-16995213
 ] 

Xinyi Yan commented on PHOENIX-5617:
------------------------------------

I tried the 4.15 client with the 4.15 server that using the sandbox, it also 
gave me the same error. After that, I checked out the `4.13-HBase-1.3` branch 
and built/tested it, and it has the same error. The latest changes in 
phoenix_sandbox file were in Jan 2016, I guess we haven't supported the 
indexing feature on the sandbox?

 
{code:java}
0: jdbc:phoenix:localhost:61182> CREATE TABLE A (A BIGINT PRIMARY KEY, B 
BIGINT, C BIGINT);
No rows affected (1.277 seconds)
0: jdbc:phoenix:localhost:61182> CREATE VIEW A_VIEW AS SELECT * FROM A;
No rows affected (0.092 seconds)
0: jdbc:phoenix:localhost:61182> CREATE INDEX A_VIEW_INDEX ON A_VIEW(B) 
INCLUDE(C);
19/12/12 15:30:49 WARN ipc.CoprocessorRpcChannel: Call failed on IOException
org.apache.hadoop.hbase.DoNotRetryIOException: 
org.apache.hadoop.hbase.DoNotRetryIOException: ERROR 0 (08001): No suitable 
driver found
 for jdbc:phoenix:localhost:61182:/hbase;test=true; A_VIEW_INDEX
{code}
 

> Phoenix Sandbox is missing the Phoenix JDBC driver.
> ---------------------------------------------------
>
>                 Key: PHOENIX-5617
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5617
>             Project: Phoenix
>          Issue Type: Test
>            Reporter: Lars Hofhansl
>            Priority: Major
>             Fix For: 4.15.1
>
>
> Various operation throw the following (or similar):
> {code:java}
> org.apache.hadoop.hbase.DoNotRetryIOException: ERROR 0 (08001): No suitable 
> driver found for jdbc:phoenix:localhost:56930:/hbase;test=true{code}
> For example creating a table with a 4.14 client, or creating a local index 
> (any client), and many more.
> If we had a more functional sandbox we can use that for some external testing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to