You can't execute "get" on a non-string row key from a shell. You need to do it through HBase Java API. Get get = new Get(toBytes("row1")); In Phoenix case, it would be difficult you to form an exact row key from the primary key values as it involves the usage of low level APIs( PTable.newKey(),PDataType.toBytes(value, column.getSortOrder) etc). However , if you are really looking for look ups, you can still do it from sql. SELECT * FROM MyTab WHERE feature='Temp' and TS=to_time('<ts_value>') ... View more

It depends on what 50K users is doing. (if your cluster capacity and configuration is right, you can scale horizontally without any problem) If it is just the point lookup(key value access) then depending upon the disk(SSD/HDD) you are using, you should be able to scale without any problem, some basic configuration tweak is required, like increasing no. of handlers for datanode and regionserver, block cache/bucket cache etc If you are doing heavy scans then you may need a large cluster which can bear this load. Network, CPU and disk will play an important role. ... View more

You can create a Schema(which is similar to databases) by using following grammar. https://phoenix.apache.org/language/index.html#create_schema Schema will be mapped to a namespace in HBase so your tables can be segregated logically as well as physically. https://phoenix.apache.org/namspace_mapping.html ... View more

It seems you are using column mapping feature(Though it is default from 4.11), which encodes column name in some encoded form of qualifier while storing in hbase , this is to save space and for better performance. Currently, we don't provide any API(as there is no standard JDBC API which exposes the details of the storage) to give you such mapping. if your application requires using the HBase qualifier directly, then I would suggest creating a table having column encoding disabled so that the column name will be used for HBase qualifier as well. CREATE TABLE test ( tag varchar(10) NOT NULL, ts DATE NOT NULL, val INTEGER CONSTRAINT pk PRIMARY KEY (tag, ts) )COLUMN_ENCODED_BYTES=0; ... View more

for the second question:- bq. Also, I want to add a table with defined column families and few qualifiers. My requirement is to store the data with qualifiers at runtime. How can I make sure to fetch the valid qualifiers while fetching particular record? You can use dynamic columns while upserting data and doing SELECT. https://phoenix.apache.org/dynamic_columns.html ... View more

Why SquirrelSQL is not able to make a connection to HBase cluster is not clear from the stack trace. would you mind enabling debugging and paste the logs here. have you tried connecting using sqlline with the same url from the same machine. ... View more

I'll not recommend updating a single component in a stack, as there will be some incompatibility and upgrade issues. I only suspect you might be hitting PHOENIX-2169 so it's better to reproduce the same issue somewhere in pre-prod/dev and see if the fix works and then replicate on production. Or, you can talk to your vendor to provide the hotfix for the same version. ... View more

You need to move your snapshot from exported directory to the directory where hbase looks for snapshots(.hbase-snapshot). so that list_snapshots and other commands(like clone_snapshot ) can work easily hadoop dfs -mv hdfs://NAME_NODE:8020/hbase/.hbase-snapshot/<snapshot_name> hdfs://NAME_NODE:8020/apps/hbase/data/.hbase-snapshot/ hdfs dfs -mv hdfs://NAME_NODE:8020/hbase/archive/data/* hdfs://NAME_NODE:8020/apps/hbase/data/archive/data/ FYI:- to list snapshot directly from remote directory hbase org.apache.hadoop.hbase.snapshot.SnapshotInfo -remote-dir hdfs://NAME_NODE:8020/hbase/ -list-snapshots ... View more

you can't authenticate using username and password in Phoenix/HBase/HDFS, the only way is to go through kerberos authentication. ... View more