Re: Query DDL from Phoenix

2015-07-13 Thread Eli Levine
The standard JDBC way is to use Connection.getMetadata(). See if that does what you need. You can also query SYSTEM.TABLE directly via Phoenix if you know what you are doing. > On Jul 13, 2015, at 4:57 PM, Kevin Verhoeven > wrote: > > Is there a way to query the table structure of user tab

Query DDL from Phoenix

2015-07-13 Thread Kevin Verhoeven
Is there a way to query the table structure of user tables from Phoenix? For example, to retrieve the CREATE TABLE syntax? Thank you, Kevin Verhoeven

Re: Problem in finding the largest value of an indexed column

2015-07-13 Thread Yufan Liu
It seems that setting MAX_FILESIZE only won't trigger split automatically (need major compaction?). Also using "split on" when creating the table to force split seems only works for String type row key. Is there any way else I can use to make the table auto split for the unit test? 2015-07-09 23:3

Exception when connecting using ./sqlline.py - version phoenix-4.4.0-HBase-1.0

2015-07-13 Thread Veerraju Tadimeti
org.apache.hadoop.hbase.DoNotRetryIOException: org.apache.hadoop.hbase.DoNotRetryIOException: SYSTEM.SEQUENCE: org.apache.hadoop.hbase.client.Scan.setRaw(Z)Lorg/apache/hadoop/hbase/client/Scan; at org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:84) at org.apache.phoenix.coproce

Re: Secondary index for narrow tables. Use it or just do "double insert"

2015-07-13 Thread Yuhao Bi
Hi, I would like to suggest you to use the phoenix secondary index. It is because, 1.You can choose global index or local index(gain a better performance). 2.Just create index on id2 and query with indexHint can save your disk space. And yes secondary index is done by coprocessor. Am I right? 20

Secondary index for narrow tables. Use it or just do "double insert"

2015-07-13 Thread Serega Sheypak
Hi, I have an immutable table with 4 columns: id1, id2, meta_id1, meta_id2. Primary key is id1, I select all fields from table "row" by id1. So it's the fastest way to get data. Second access path is to select by id2. I have serious mixed workload. What is better: 1. use secondary index for id2 2

Re: HBase + Phoenix for CDR

2015-07-13 Thread Matjaž Trtnik
Actually I was thinking about doing this and use UNION ALL as it’s now supported. I haven’t had time to test this yet but will do in near future. Can anyone tell me is there any limitation when doing query and UNION ALL in number of unions you can do? Will this work out at decent speed when doing