See http://phoenix.apache.org/language/index.html#condition. Your "traditional sql" approach works with Apache Phoenix. > create table foo(s varchar, pk integer not null primary key); > upsert into foo values('abcd_bar', 1); > upsert into foo values('dcba_bar', 2); > select * from foo where s like 'abcd%'; This will return +-----------+-----+ | S | PK | +-----------+-----+ | abcd_bar | 1 | +-----------+-----+ ... View more

A few things: It looks like your HDFS is not healthy. Can you run `hdfs fsck` on the file "/apps/hbase/data1/.hbase-snapshot/S3LINKS-AIM-SNAPSHOT-NEW/.snapshotinfo"? Regarding the offline region "CUTOFF8,,1465897349742.2077c5dfbfb97d67f09120e4b9cdc15a.", you can check the RegionServer logs on data1.corp.mirrorplus.com. Also, you can try to grep the HBase master log for "2077c5dfbfb97d67f09120e4b9cdc15a", looking for the last "OPEN" location. The HBase master UI might also tell you if this region is stuck in transition (RIT). If so, `hbase hbck` should be able to help you. ... View more

org.apache.hadoop.net.ConnectTimeoutException: 10000 millis timeout while waiting for channel to be ready for connect. ch : java.nio.channels.SocketChannel[connection-pending remote=ip-172-31-15-225.us-west-2.compute.internal/52.32.173.25:16000] Can you connect to this IP address and port on your local machine using telnet/netcat? e.g. telnet 52.32.173.25 16000 You should get a message "Connected to <host>" and not "Connection refused". If you get the "Connection refused" message, it is likely some firewall or networking issue (like @Ankit Singhal pointed out) ... View more

There are two sides here. The documentation that you listed and @ssoldatov confirmed are accurate for PQS to connect to HBase. The other side, which is likely missing as "official" Apache Phoenix documentation, is the thin-client configuration properties. These properties are presently available at http://calcite.apache.org/avatica/docs/client_reference.html. The sqlline-thin.py script will automatically configure them for you, but you would have to provide them when using the thin JDBC driver directly. In practice, it would look something like the following when you have already performed a Kerberos login jdbc:phoenix:thin:url=<scheme>://<server-hostname>:<port>;authentication=SPNEGO Alternatively, you can provide a principal and keytab which the thin driver will use to login automatically: jdbc:phoenix:thin:url=<scheme>://<server-hostname>:<port>;authentication=SPNEGO;principal=my_user;keytab=/home/my_user/my_user.keytab ... View more